[openssl-dev] [openssl.org #4609] Configure does not honor requests for ld.gold

[Matt Caswell via RT]

On Wed Aug 17 16:18:26 2016, levitte wrote:
> On Fri Jul 08 09:36:42 2016, levitte wrote:
> > On Fri Jul 08 09:33:01 2016, noloa...@gmail.com wrote:
> > > 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
> >
> > Did it work for you when doing this?
> >
> > ./config -fuse-ld=gold
>
> Jeff, please respond.

Still, no response so assuming this is an acceptable work around. Closing this
ticket.

Matt

-- 
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

[openssl-dev] [openssl.org #4609] Configure does not honor requests for ld.gold

[Richard Levitte via RT]

On Fri Jul 08 09:36:42 2016, levitte wrote:
> On Fri Jul 08 09:33:01 2016, noloa...@gmail.com wrote:
> > 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
>
> Did it work for you when doing this?
>
> ./config -fuse-ld=gold

Jeff, please respond.

--
Richard Levitte
levi...@openssl.org

-- 
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

Re: [openssl-dev] [openssl.org #4609] Configure does not honor requests for ld.gold

[Andy Polyakov via RT]

>> I don't know what you expect us to do.  We don't use the LD variable.
> 
> Right. I'm just pointing out gaps.
> 
> It only gets worse for users. What happens when someone tries a
> cross-compile by setting CC, AR, RANLIB, LD and a CFLAGS with
> --sysroot? As far as I know, there is no RTFM for cross-compiles.

Can there be one? Do we know that *all* cross-compile environments are
so similar that one can actually formulate universal TFM? Well, I'm not
saying that it's impossible to be more "eloquent" than to mention
--cross-compile-prefix and CROSS_COMPILE variable in ./INSTALL and
discuss them more specifically in Configurations/10-main.cf for Android
and iOS, I only question how "F" a "TFM" can really get. You say "it
only gets worse for users." Well, what users? For example today Debian
users can have it really simple by installing prepackaged cross
compilers along with cross-dev packages and just specify
--cross-compile-prefix alone, no need to bother with --sysroot or
anything. Moreover, if you are creative enough you can even note that if
you install qemu-user, arrange binfmt and set some variables (or create
some symbolic links) you'll be able to execute resulting alien Linux
binaries as if they were native directly from your shell prompt...
Bottom line is that there are so many variables that apparent gaps are
kind of inevitable...


-- 
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

Re: [openssl-dev] [openssl.org #4609] Configure does not honor requests for ld.gold

[noloa...@gmail.com via RT]

On Fri, Jul 8, 2016 at 8:33 AM, Salz, Rich via RT  wrote:
> I don't know what you expect us to do.  We don't use the LD variable.

Right. I'm just pointing out gaps.

It only gets worse for users. What happens when someone tries a
cross-compile by setting CC, AR, RANLIB, LD and a CFLAGS with
--sysroot? As far as I know, there is no RTFM for cross-compiles.

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

Re: [openssl-dev] [openssl.org #4609] Configure does not honor requests for ld.gold

[Salz, Rich via RT]

I don't know what you expect us to do.  We don't use the LD variable.



-- 
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

[openssl-dev] [openssl.org #4609] Configure does not honor requests for ld.gold

[Richard Levitte via RT]

On Fri Jul 08 09:33:01 2016, noloa...@gmail.com wrote:
> 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

Did it work for you when doing this?

./config -fuse-ld=gold

--
Richard Levitte
levi...@openssl.org

-- 
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

Re: [openssl-dev] [openssl.org #4609] Configure does not honor requests for ld.gold

[noloa...@gmail.com via RT]

On Fri, Jul 8, 2016 at 4:33 AM, Richard Levitte via RT  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 (0x0x1016L)
>> 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

[openssl-dev] [openssl.org #4609] Configure does not honor requests for ld.gold

[Richard Levitte via RT]

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 (0x0x1016L)
> 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.

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.

That being said, have you tried the following (the configuration scripts will
assume that any argument starting with a dash that they don't understand
internally are to be taken as C flags... this too has been pointed out before)?

./config -fuse-ld=gold

Cheers,
Richard

--
Richard Levitte
levi...@openssl.org

-- 
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

[openssl-dev] [openssl.org #4609] Configure does not honor requests for ld.gold

[noloa...@gmail.com via RT]

$ ./config LD=ld.gold
Operating system: x86_64-whatever-linux2
Configuring for linux-x86_64
Configuring OpenSSL version 1.1.0-pre6-dev (0x0x1016L)
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).


-- 
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