[Buildroot] lame linking issue
Yegor Yefremov
yegor_sub1 at visionsystems.de
Tue Jul 5 10:01:40 UTC 2011
Am 05.07.2011 11:24, schrieb Peter Korsgaard:
>>>>>> "Yegor" == Yegor Yefremov <yegor_sub1 at visionsystems.de> writes:
> Hi,
>
> Yegor> Could it be due to 64-bit build system?
>
> No - I build on 64bit (Debian) as well.
>
> Yegor> /bin/sh ../libtool --tag=CC --mode=link /home/YegorYefremov/projects/versioned/buildroot/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-gcc -Wall -pipe -pipe -Os -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib64/glib/include -o lame main.o console.o get_audio.o lametime.o parse.o portableio.o timestatus.o brhist.o ../libmp3lame/libmp3lame.la -lm
>
> It's probably the /usr/include and /usr/lib64 references here that's
> causing problems. I wonder where they are coming from though, as I don't
> see any glib/gtk references in lame's configure script
The references are there in output/build/lame-3.98.4/configure
More information about the buildroot
mailing list