[solved] Problem with libtool?

ngoonee · 2009-09-30 22:55:49

Hi all, while compiling pulseaudio-git I get this log from makepkg (warning, 1.7k lines):-

It managed to compile fine without -Wl,--as-needed. However, when I asked on the pulseaudio ML, the dev pointed up this line in my log (line 1700):-
libtool: link: not configured to extract global symbols from dlpreopened files

He mentioned there's probably a bug in libtool, or perhaps in our particular binary. Should I submit a bug report, or is there a simple "reason'' anyone knows of?

Last edited by ngoonee (2009-10-01 01:45:49)

Allan · 2009-09-30 23:12:02

I have only ever seen that when cross compiling:

configure: WARNING: If you wanted to set the --build type, don't use --host.
    If a cross compiler is detected then cross compile mode will be used.
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for x86_64-pc-linux-gnu-strip... no
checking for strip... strip
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking how to create a pax tar archive... gnutar
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for x86_64-pc-linux-gnu-gcc... no

ngoonee · 2009-10-01 00:03:45

Allan wrote:

I have only ever seen that when cross compiling:

configure: WARNING: If you wanted to set the --build type, don't use --host.
    If a cross compiler is detected then cross compile mode will be used.
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for x86_64-pc-linux-gnu-strip... no
checking for strip... strip
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking how to create a pax tar archive... gnutar
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for x86_64-pc-linux-gnu-gcc... no

In this case, the thing is that my CHOST is x86_64-pc-linux-gnu, while some packages seem to require x86_64-unknown-linux-gnu, probably due to the search for $CHOST-gcc. I can't remember whether I have previously modified this CHOST value. If I attempt to compile by manually setting CHOST inside the PKGBUILD, it works, though I'm not sure if the libtool error still comes out. Regardless, does this mean libtool is working fine?

EDIT: I was just searching CHOST on our wiki, and perhaps I'd changed my CHOST to x86_64-pc-linux-gnu following this wiki article. Again, I can't remember.... What's the 'correct' value for CHOST on a 64-bit system?

Last edited by ngoonee (2009-10-01 00:17:25)

Allan · 2009-10-01 01:33:13

This is the default:

CHOST="x86_64-unknown-linux-gnu"

Edit: that wiki article is weird...

ngoonee · 2009-10-01 01:38:15

Allan wrote:

This is the default:
CHOST="x86_64-unknown-linux-gnu"
Edit: that wiki article is weird...

well, its 'in the wiki'. Sounds religious, said that way. Let me know here if that's not correct, I'll make the appropriate wiki changes (and changes in my system, of course).

Allan · 2009-10-01 01:40:51

I'd recommend sticking with what the x86_64 gcc is built for....

> gcc -v
Using built-in specs.
Target: x86_64-unknown-linux-gnu

Feel free to fix the wiki

ngoonee · 2009-10-01 01:45:35

Allan wrote:

Feel free to fix the wiki

Changed. Thanks.

Arch Linux

#1 2009-09-30 22:55:49

[solved] Problem with libtool?

#2 2009-09-30 23:12:02

Re: [solved] Problem with libtool?

#3 2009-10-01 00:03:45

Re: [solved] Problem with libtool?

#4 2009-10-01 01:33:13

Re: [solved] Problem with libtool?

#5 2009-10-01 01:38:15

Re: [solved] Problem with libtool?

#6 2009-10-01 01:40:51

Re: [solved] Problem with libtool?

#7 2009-10-01 01:45:35

Re: [solved] Problem with libtool?

Board footer