tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: binutils/

On Sat, 19 Nov 2016, coypu%SDF.ORG@localhost wrote:
On Sat, Nov 19, 2016 at 05:54:44PM +0000, David Holland wrote:
So it seems (see PR 50988) that binutils/ doesn't check
USE_BUILTIN.binutils, so including it will always use pkgsrc binutis
regardless of builtin processing.

Whether this is a bug or not seems open to interpretation - I would
say that it is, because it will probably cause builds to fail if
builtin processing results in not installing pkgsrc binutils at all.
On the other hand, if it's supposed to override the default as it
ought to override the default as.

Opinions? There's only the one use of it in pkgsrc, so it's not
exactly a critical issue.

(It also looks like the builtin processing isn't checking the binutils
version, which means that pulling in pkgsrc binutils and setting a
specific version requirement won't work. The chief reason one might
want to force the use of pkgsrc binutils is to get a version that
understands some particular set of new extension instructions, so
unless I'm missing something this also seems like a problem.)

I think sborrill encountered this issue when trying to use newer
binutils for pkgsrc on netbsd-5.

My problem was related, but not the same. In fact, I used as an exemplar of how my problem might be solved.

IIRC I found when building multimedia/libvpx that it would always try to use builtin ld because gcc is built with --with-ld=/usr/bin/ld and so PATH
is ignored. I suggested one of the following solutions:

1) Create a devel/binutils/ in a similar vein to devel/binutils/ that overrides gcc specs to force a different ld to use

2) If on NetBSD < 6 (and other OSes too, I suspect), enforce the link between binutils and pkgsrc gcc so that the linker from binutils is always used.


Home | Main Index | Thread Index | Old Index