GNU bug report logs -
#17294
Bug - nm_test_func check is confused with -flto
Previous Next
To reply to this bug, email your comments to 17294 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-libtool <at> gnu.org
:
bug#17294
; Package
libtool
.
(Fri, 18 Apr 2014 16:35:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Martin Liška <mliska <at> suse.cz>
:
New bug report received and forwarded. Copy sent to
bug-libtool <at> gnu.org
.
(Fri, 18 Apr 2014 16:35:03 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hello,
starting with GCC 4.9.0, compiler will use just slim objects files
during LTO compilation. That means, no assembly output is put to object
files. I noticed that libtool uses nm tools to extract symbol from
object file: http://pastebin.com/RF1VubdR. Would it be possible to add
-fno-lto for this check?
I think there should be added '-fno-lto' at line 14:
(eval $ac_compile -fno-lto) 2>&5
What do you think about that?
Thank you,
Martin
Information forwarded
to
bug-libtool <at> gnu.org
:
bug#17294
; Package
libtool
.
(Sat, 17 May 2014 00:47:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 17294 <at> debbugs.gnu.org (full text, mbox):
On 2014-04-18 15:01, Martin Liška wrote:
> Hello,
> starting with GCC 4.9.0, compiler will use just slim objects files during LTO compilation. That means, no assembly output is put to object files. I noticed that libtool uses nm tools to extract symbol from object file: http://pastebin.com/RF1VubdR. Would it be possible to add -fno-lto for this check?
>
> I think there should be added '-fno-lto' at line 14:
> (eval $ac_compile -fno-lto) 2>&5
>
> What do you think about that?
Hi, and sorry for the late response.
I think that it is not possible to blindly add -fno-lto without knowing
if the compiler understands -fno-lto.
Changing this takes more effort, sorry.
Cheers,
Peter
Information forwarded
to
bug-libtool <at> gnu.org
:
bug#17294
; Package
libtool
.
(Tue, 20 May 2014 11:33:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 17294 <at> debbugs.gnu.org (full text, mbox):
On 05/17/2014 02:46 AM, Peter Rosin wrote:
> On 2014-04-18 15:01, Martin Liška wrote:
>> Hello,
>> starting with GCC 4.9.0, compiler will use just slim objects files during LTO compilation. That means, no assembly output is put to object files. I noticed that libtool uses nm tools to extract symbol from object file: http://pastebin.com/RF1VubdR. Would it be possible to add -fno-lto for this check?
>>
>> I think there should be added '-fno-lto' at line 14:
>> (eval $ac_compile -fno-lto) 2>&5
>>
>> What do you think about that?
> Hi, and sorry for the late response.
>
> I think that it is not possible to blindly add -fno-lto without knowing
> if the compiler understands -fno-lto.
>
> Changing this takes more effort, sorry.
>
> Cheers,
> Peter
>
Hello,
I understand that suggested option is probably simple. How can we
decorate some LTO sensitive checks with -flto if supported by a compiler?
Thanks,
Martin
Information forwarded
to
bug-libtool <at> gnu.org
:
bug#17294
; Package
libtool
.
(Wed, 04 Jun 2014 09:16:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 17294 <at> debbugs.gnu.org (full text, mbox):
On 05/17/2014 02:46 AM, Peter Rosin wrote:
> On 2014-04-18 15:01, Martin Liška wrote:
>> Hello,
>> starting with GCC 4.9.0, compiler will use just slim objects files during LTO compilation. That means, no assembly output is put to object files. I noticed that libtool uses nm tools to extract symbol from object file: http://pastebin.com/RF1VubdR. Would it be possible to add -fno-lto for this check?
>>
>> I think there should be added '-fno-lto' at line 14:
>> (eval $ac_compile -fno-lto) 2>&5
>>
>> What do you think about that?
> Hi, and sorry for the late response.
>
> I think that it is not possible to blindly add -fno-lto without knowing
> if the compiler understands -fno-lto.
Hello Peter,
I would appreciate any kind of help connected to configure script to be able to support -flto.
My suggestion:
1) we can detect if a compiler supports -flto
2) if so, we can define $ac_compile_without_lto = "$ac_compile -fno-lto"
3) otherwise, $ac_compile_without_lto = $ac_compile
What do you think about it?
Today, I found out another packages suffering from the same problem.
Thanks,
Martin
>
> Changing this takes more effort, sorry.
>
> Cheers,
> Peter
>
This bug report was last modified 11 years and 13 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.