Martin Liška wrote:
[SNIP]
However, LTO breaks nm really badly and with -fno-common this variable
gets marked as "T" in the nm output.
Thank you for identification of the root cause. I've just created a
nm issue
for that:
https://sourceware.org/bugzilla/show_bug.cgi?id=25355
It is clear
On 2020-01-08, Martin Liška wrote:
> On 1/7/20 10:40 PM, Nick Bowler wrote:
>> Regardless, $global_symbol_pipe is part of the documented libtool
>> interface, which says you can do:
>>
>>eval "$NM progname | $global_symbol_pipe"
>>
>> This is obviously busted because the failed configure test
On 1/8/20 10:16 AM, Martin Liška wrote:
On 1/7/20 9:47 PM, Nick Bowler wrote:
On 1/7/20, Martin Liška wrote:
nm -B detection fails to be detected with -flto and -fno-common CFLAGS:
configure:6307: checking command to parse /usr/bin/nm -B output from gcc
object
[...]
configure:6536: gcc -o
On 1/7/20 10:40 PM, Nick Bowler wrote:
On 1/7/20, Bob Friesenhahn wrote:
On Tue, 7 Jan 2020, Nick Bowler wrote:
On 1/7/20, Martin Liška wrote:
nm -B detection fails to be detected with -flto and -fno-common CFLAGS:
I don't know what vintage this documentation is (the copyright says it
is
On 1/7/20 10:07 PM, Bob Friesenhahn wrote:
On Tue, 7 Jan 2020, Nick Bowler wrote:
On 1/7/20, Martin Liška wrote:
nm -B detection fails to be detected with -flto and -fno-common CFLAGS:
I don't know what vintage this documentation is (the copyright says it is from 2020 so it
seems to be
On 1/7/20 9:47 PM, Nick Bowler wrote:
On 1/7/20, Martin Liška wrote:
nm -B detection fails to be detected with -flto and -fno-common CFLAGS:
configure:6307: checking command to parse /usr/bin/nm -B output from gcc
object
[...]
configure:6536: gcc -o conftest -O2 -Wall -D_FORTIFY_SOURCE=2
On 2020-01-07, Nick Bowler wrote:
> On 1/7/20, Martin Liška wrote:
>> nm -B detection fails to be detected with -flto and -fno-common CFLAGS:
>>
>> configure:6307: checking command to parse /usr/bin/nm -B output from gcc
>> object
> [...]
>> configure:6536: gcc -o conftest -O2 -Wall
On 2020-01-07, Nick Bowler wrote:
>>> I'm not 100% sure which libtool features will be affected by this
>>> configuration failure. It doesn't fatally stop the configure script.
>>> Probably dlpreopen won't work at all?
>>
>> Are there many users of dlpreopen()?
>
> I imagine there are users of
On 1/7/20, Bob Friesenhahn wrote:
> On Tue, 7 Jan 2020, Nick Bowler wrote:
>
>> On 1/7/20, Martin Liška wrote:
>>> nm -B detection fails to be detected with -flto and -fno-common CFLAGS:
>
> I don't know what vintage this documentation is (the copyright says it
> is from 2020 so it seems to be
On Tue, 7 Jan 2020, Nick Bowler wrote:
On 1/7/20, Martin Liška wrote:
nm -B detection fails to be detected with -flto and -fno-common CFLAGS:
I don't know what vintage this documentation is (the copyright says it
is from 2020 so it seems to be the latest), but the page at
On 1/7/20, Martin Liška wrote:
> nm -B detection fails to be detected with -flto and -fno-common CFLAGS:
>
> configure:6307: checking command to parse /usr/bin/nm -B output from gcc
> object
[...]
> configure:6536: gcc -o conftest -O2 -Wall -D_FORTIFY_SOURCE=2
> -fstack-protector-strong
Hello.
nm -B detection fails to be detected with -flto and -fno-common CFLAGS:
configure:6307: checking command to parse /usr/bin/nm -B output from gcc object
configure:6460: gcc -c -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong
-funwind-tables -fasynchronous-unwind-tables
12 matches
Mail list logo
