libm compilation failing in -current

[John Klos]

Hi,

Can anyone help me to learn why libm is failing? I'm using a netbsd-5
system to compile -current, and it fails here:

#     build  libm/libm.so.0.7
rm -f libm.so.0.7
/usr/current/src/../tools/bin/m68k--netbsdelf-gcc  -Wl,-nostdlib
-B/usr/current/src/../dest-amiga/usr/lib/
-B/usr/current/src/../dest-amiga/usr/lib/  -Wl,-x -shared
-Wl,-soname,libm.so.0 -Wl,--warn-shared-textrel -o libm.so.0.7
-Wl,--whole-archive libm_pic.a  -Wl,--no-whole-archive
-Wl,-rpath-link,/usr/current/src/../dest-amiga/lib:/usr/current/src/../dest-amiga/usr/lib
-R/lib  -L/usr/current/src/../dest-amiga/lib  -Wl,--fatal-warnings
-L/usr/current/src/../dest-amiga/usr/lib
/usr/current/tools/bin/../lib/gcc/m68k--netbsdelf/4.1.3/../../../../m68k--netbsdelf/bin/ld:
warning: creating a DT_TEXTREL in a shared object.
collect2: ld returned 1 exit status
*** [libm.so.0.7] Error code 1

I'm not sure how this is supposed to be fixed, especially since the
"--warn-shared-textrel" seems to have been explicitely added. Any ideas?

John Klos

[Nick Hudson-4]

On Wednesday 04 November 2009 09:02:58 John Klos wrote:
> Hi,
>
> Can anyone help me to learn why libm is failing? I'm using a netbsd-5
> system to compile -current, and it fails here:

I builds for me on a NetBSD/i386 netbsd-5 machine.

Do you have any local diffs? Did you try a clean build?

> #     build  libm/libm.so.0.7
> rm -f libm.so.0.7
> /usr/current/src/../tools/bin/m68k--netbsdelf-gcc  -Wl,-nostdlib
> -B/usr/current/src/../dest-amiga/usr/lib/
> -B/usr/current/src/../dest-amiga/usr/lib/  -Wl,-x -shared
> -Wl,-soname,libm.so.0 -Wl,--warn-shared-textrel -o libm.so.0.7
> -Wl,--whole-archive libm_pic.a  -Wl,--no-whole-archive
> -Wl,-rpath-link,/usr/current/src/../dest-amiga/lib:/usr/current/src/../dest
>-amiga/usr/lib -R/lib  -L/usr/current/src/../dest-amiga/lib
> -Wl,--fatal-warnings -L/usr/current/src/../dest-amiga/usr/lib
> /usr/current/tools/bin/../lib/gcc/m68k--netbsdelf/4.1.3/../../../../m68k--n
>etbsdelf/bin/ld: warning: creating a DT_TEXTREL in a shared object.
> collect2: ld returned 1 exit status
> *** [libm.so.0.7] Error code 1
>
> I'm not sure how this is supposed to be fixed, especially since the
> "--warn-shared-textrel" seems to have been explicitely added. Any ideas?

Look for the relocation against in the .text segment using readelf / objdump
against the library to find which bit of code it's in. Usually it's either
code that's compiled without -fPIC or non-PIC assembler.

>
> John Klos

Nick

[Christos Zoulas-2]

In article <200911041319.54690.nick.hudson@...>,
Nick Hudson  <nick.hudson@...> wrote:

>On Wednesday 04 November 2009 09:02:58 John Klos wrote:
>> Hi,
>>
>> Can anyone help me to learn why libm is failing? I'm using a netbsd-5
>> system to compile -current, and it fails here:
>
>I builds for me on a NetBSD/i386 netbsd-5 machine.
>
>Do you have any local diffs? Did you try a clean build?
>
>> #     build  libm/libm.so.0.7
>> rm -f libm.so.0.7
>> /usr/current/src/../tools/bin/m68k--netbsdelf-gcc  -Wl,-nostdlib
>> -B/usr/current/src/../dest-amiga/usr/lib/
>> -B/usr/current/src/../dest-amiga/usr/lib/  -Wl,-x -shared
>> -Wl,-soname,libm.so.0 -Wl,--warn-shared-textrel -o libm.so.0.7
>> -Wl,--whole-archive libm_pic.a  -Wl,--no-whole-archive
>> -Wl,-rpath-link,/usr/current/src/../dest-amiga/lib:/usr/current/src/../dest
>>-amiga/usr/lib -R/lib  -L/usr/current/src/../dest-amiga/lib
>> -Wl,--fatal-warnings -L/usr/current/src/../dest-amiga/usr/lib
>> /usr/current/tools/bin/../lib/gcc/m68k--netbsdelf/4.1.3/../../../../m68k--n
>>etbsdelf/bin/ld: warning: creating a DT_TEXTREL in a shared object.
>> collect2: ld returned 1 exit status
>> *** [libm.so.0.7] Error code 1
>>
>> I'm not sure how this is supposed to be fixed, especially since the
>> "--warn-shared-textrel" seems to have been explicitely added. Any ideas?
>
>Look for the relocation against in the .text segment using readelf / objdump
>against the library to find which bit of code it's in. Usually it's either
>code that's compiled without -fPIC or non-PIC assembler.
>
>>
>> John Klos

I had added code that printed the symbol causing the error in the previous
binutils, why don't we port this code forward?

christos

[Nick Hudson-4]

On Wednesday 04 November 2009 23:32:39 Christos Zoulas wrote:
[snip]

> I had added code that printed the symbol causing the error in the previous
> binutils, why don't we port this code forward?

Oh, I did bring your i386 change forward. I'll look to adding a similar change
everywhere.

> christos

Nick

[Christos Zoulas]

On Nov 5,  7:47am, nick.hudson@... (Nick Hudson) wrote:
-- Subject: Re: libm compilation failing in -current

| On Wednesday 04 November 2009 23:32:39 Christos Zoulas wrote:
| [snip]
|
| > I had added code that printed the symbol causing the error in the previous
| > binutils, why don't we port this code forward?
|
| Oh, I did bring your i386 change forward. I'll look to adding a similar change
| everywhere.
|
| > christos

great, thanks!

christos

[John Klos]

>> Can anyone help me to learn why libm is failing? I'm using a netbsd-5
>> system to compile -current, and it fails here:
>
> I builds for me on a NetBSD/i386 netbsd-5 machine.
>
> Do you have any local diffs? Did you try a clean build?

I just tried a completely fresh tree on an amd64 system and got the same
issue. I'm about to try on a macppc machine.

John