On Fri, Jul 8, 2016 at 4:33 AM, Richard Levitte via RT <r...@openssl.org> wrote: > On Fri Jul 08 07:47:14 2016, noloa...@gmail.com wrote: >> $ ./config LD=ld.gold >> Operating system: x86_64-whatever-linux2 >> Configuring for linux-x86_64 >> Configuring OpenSSL version 1.1.0-pre6-dev (0x0x10100006L) >> target already defined - linux-x86_64 (offending arg: LD=ld.gold) >> >> And: >> >> $ LD=ld.gold ./config >> Operating system: x86_64-whatever-linux2 >> Configuring for linux-x86_64 >> ... >> >> $ cat Makefile | grep ld.gold >> $ cat Makefile.shared | grep ld.gold >> $ >> >> I don't believe CFLAG -fuse-ld=gold is an option because the linker is >> invoked directly rather than using the compiler driver. (Or at least >> it used to be that way). > > 'ld' is only used in one case, in Makefile.shared. That's for AIX, when > building shared objects directly from object files instead of going from the > static library. Therefore, trying to set LD makes absolutely no sense.
Hmmm... If I want to use ld.gold as my linker, the easiest path is to set LD=ld.gold. It makes perfect sense to some.... > Also, please please please read INSTALL, it tells you what environment > variables are considered by the configuration scripts, and please please > please > understand that our configuration scripts are not autoconf generated ones and > currently do not understand 'FOO=value' arguments. This has been pointed out > quite a few times already. Why be normal :) ... but I understand why it does not make perfect sense to others. Jeff -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4609 Please log in as guest with password guest if prompted -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev