Bug 203757 - jam-based ports (eg: graphics/argyllcms) fail to build when using ports binutils.
Summary: jam-based ports (eg: graphics/argyllcms) fail to build when using ports binut...
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Koop Mast
Keywords: needs-patch, needs-qa
Depends on:
Reported: 2015-10-14 04:09 UTC by Justin Hibbits
Modified: 2020-05-26 13:59 UTC (History)
5 users (show)

See Also:
koobs: maintainer-feedback? (kwm)

Failure log for argyllcms, which requires a C11 compiler, pulling in ports binutils on non-clang platforms (20.96 KB, text/plain)
2015-10-14 04:09 UTC, Justin Hibbits
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Justin Hibbits freebsd_committer 2015-10-14 04:09:25 UTC
Created attachment 162010 [details]
Failure log for argyllcms, which requires a C11 compiler, pulling in ports binutils on non-clang platforms

Somewhere devel/jam calls ar with -n, either directly or indirectly.  Base ar can handle this, but ports binutils cannot.  I think this may be related to the elftoolchain import for head, but can't be sure.  Attached the failure log for one port.
Comment 1 Ed Maste freebsd_committer 2015-10-15 14:34:34 UTC
Base system ar does not come from ELF Tool Chain so I doubt it's related.
Comment 2 Justin Hibbits freebsd_committer 2015-10-15 15:08:09 UTC
This is actually caused by setting ${AR}.  Jambase conditionally sets it to 'ar ru', but it's already overridden by the ports framework, set to /usr/local/bin/ar, so 'ru' is not added, resulting in this error.
Comment 3 Kubilay Kocak freebsd_committer freebsd_triage 2015-10-15 15:34:28 UTC
CC graphics/argyllcms MAINTAINER
Comment 4 Martin Wilke freebsd_committer 2015-12-24 21:12:07 UTC
Over to maintainer.
Comment 5 russo 2016-04-05 05:49:24 UTC
Has there been any work on this yet?  Various ports (gtk30, cups) have started defaulting to build with "colord" (which requires argyllcms), and these all fail on Freebsd 9.3 due to the /usr/local/bin/ld issue reported here.

Fortunately, one can turn off COLORD in all of these ports and get past the problem, but the reduction in functionality could be problematic.
Comment 6 russo 2016-04-11 22:07:16 UTC
It appears that disabling COLORD in the gtk30 and cups ports actually breaks printing, which is failing due to inability to access '.icc" files.

Fixing argyllcms so that it can build under FreeBSD 9.x would be great.

And of course in comment 5 I meant to refer to the "/usr/local/bin/ar issue", not the "/usr/local/bin/ld issue."
Comment 7 Walter Schwarzenfeld freebsd_triage 2018-01-17 07:19:52 UTC
Is this still relevant?
Comment 8 Justin Hibbits freebsd_committer 2018-01-17 17:03:27 UTC
I think a similar Jambase patch should be applied to the other jam-using ports as was committed to argyllcms in ports r440675.
Comment 9 Mark Linimon freebsd_committer freebsd_triage 2018-02-25 06:08:42 UTC
(In reply to Justin Hibbits from comment #8)

Is there a list of these ports?
Comment 10 Walter Schwarzenfeld freebsd_triage 2018-06-03 19:47:49 UTC
Comment 11 Mark Linimon freebsd_committer freebsd_triage 2018-06-03 19:49:23 UTC
(In reply to w.schwarzenfeld from comment #10)

devel/p4 and devel/p4api have been deleted from the ports tree.
Comment 12 Walter Schwarzenfeld freebsd_triage 2018-06-03 19:58:18 UTC
I have it still in the portstree and no entry in /usr/ports/MOVED.
Comment 13 Mark Linimon freebsd_committer freebsd_triage 2018-06-03 20:47:26 UTC
(In reply to w.schwarzenfeld from comment #12)

Apparently this is simply a brain-glitch on my part.
Comment 14 Mark Linimon freebsd_committer freebsd_triage 2020-05-26 00:32:55 UTC
Is this PR still relevant?
Comment 15 Justin Hibbits freebsd_committer 2020-05-26 13:59:37 UTC
Looks like all packages listed in comment #10 build for powerpc64 on stable/12.