Using LFS 7.7, I have run into a problem building
vorbis-tools-1.4.0 using the instructions in the svn version of the BLFS
book.

I get this error building in the ogg123 directory:

/bin/sh ../libtool --tag=CC --mode=link gcc  -O2 -Wall -ffast-math
-fsigned-char -g -O2   -o ogg123  audio.o buffer.o callbacks.o
cfgfile_options.o cmdline_options.o file_transport.o format.o
http_transport.o ogg123.o oggvorbis_format.o playlist.o status.o
remote.o transport.o vorbis_comments.o
vgfilter.o ../share/libutf8.a ../share/libgetopt.a -lvorbisfile
-lvorbis  -logg  -lao -lnsl   -lcurl -lpthread libtool: link: gcc -O2
-Wall -ffast-math -fsigned-char -g -O2 -o ogg123 audio.o buffer.o
callbacks.o cfgfile_options.o cmdline_options.o file_transport.o
format.o http_transport.o ogg123.o oggvorbis_format.o playlist.o
status.o remote.o transport.o vorbis_comments.o
vgfilter.o  ../share/libutf8.a ../share/libgetopt.a /usr/lib/libvorbisfile.so 
/usr/lib/libvorbis.so /usr/lib/libogg.so /usr/lib/libao.so
-lnsl /usr/lib/libcurl.so -lpthread /usr/bin/ld: vgfilter.o: undefined
reference to symbol '__pow_finite@@GLIBC_2.15' /lib64/libm.so.6: error
adding symbols: DSO missing from command line

Apparently the linker isn't using libm, or at least not finding what it
wants in libm.so.6 

libm exists in /lib64:
0 [ /lib64 ]$ ls -l libm.*
lrwxrwxrwx 1 root root 12 Mar  2 17:08 libm.so.6 -> libm-2.21.so
0 [ /lib64 ]$ ls -l libm-2.21.so
-rwxr-xr-x 1 root root 1135304 Mar  3 17:51 libm-2.21.so

But what does 'DSO missing from command line' mean?

Since I can get around the problem using 'make LDFLAGS=-lm', this
suggests to me that the library itself is fine. But obviously something
is wrong in the toolchain - despite this being the first such error, 
not arising until the 333rd package/library/whatever built since
completing the base LFS 7.7

Where should  I be looking?

Thanks
Gordon
---
Gordon Findlay
[email protected]
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to