Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 27 Mar 2010 00:21:42 +0000
From:      CeDeROM <tomek.cedro@gmail.com>
To:        Rene Ladan <r.c.ladan@gmail.com>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: default binutils - linker 2.15 versus 2.20
Message-ID:  <3fcfb0ba1003261721k2e05913ah3ebe32f4dba90635@mail.gmail.com>
In-Reply-To: <e890cae61003260019u2bf532f7oaf61b305f786216a@mail.gmail.com>
References:  <3fcfb0ba1003251803p15b4012exf8cae140c6f88d32@mail.gmail.com> <e890cae61003260019u2bf532f7oaf61b305f786216a@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 26, 2010 at 7:19 AM, Rene Ladan <r.c.ladan@gmail.com> wrote:
> 2010/3/26 CeDeROM <tomek.cedro@gmail.com>:
>> Hello world!
>>
>> I have problems building applications requiring ld 2.20 (located at
>> /usr/local/bin) where ld 2.15 (located at /usr/bin) is being invoked
>> with c++ (gcc4.2.1). Why there are two linkers on the system? Is it
>> possible to update the default linker to version 2.20?
>>
> An upgrade is not possible because binutils switched to GPL3 after
> version 2.17 and GLP3 code is not allowed in the base system. =C2=A0One
> possible solution would be to tell the applications to use
> /usr/local/bin/ld explicitly.

Hello Rene! Thank you for this information, but this complicates my
build process dramaticaly. Maybe you know how to force /usr/bin/c++ to
use /usr/local/bin/ld instead of /usr/local/bin (possibly executable
from a port build process)..? Someone had to have similar problem
before - to use newer linker than the system default...

Best regards,
Tomek
--=20
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3fcfb0ba1003261721k2e05913ah3ebe32f4dba90635>