From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: buildroot@busybox.net
Subject: [Buildroot] lame linking issue
Date: Tue, 05 Jul 2011 12:12:18 +0200 [thread overview]
Message-ID: <4E12E382.6050602@visionsystems.de> (raw)
In-Reply-To: <8762nhvy1n.fsf@macbook.be.48ers.dk>
> 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
>
> Yegor> The references are there in output/build/lame-3.98.4/configure
>
> There's indeed a gtk-1.2 reference. Do you have gtk-config on your host?
Yes, I have.
next prev parent reply other threads:[~2011-07-05 10:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 13:56 [Buildroot] lame linking issue Yegor Yefremov
2011-07-01 14:44 ` hariharan veerappan
2011-07-01 14:49 ` Yegor Yefremov
2011-07-05 8:39 ` Peter Korsgaard
2011-07-05 9:06 ` Yegor Yefremov
2011-07-05 9:24 ` Peter Korsgaard
2011-07-05 10:01 ` Yegor Yefremov
2011-07-05 10:09 ` Peter Korsgaard
2011-07-05 10:12 ` Yegor Yefremov [this message]
2011-07-05 11:28 ` Peter Korsgaard
2011-07-05 12:06 ` Yegor Yefremov
2011-07-05 13:01 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E12E382.6050602@visionsystems.de \
--to=yegor_sub1@visionsystems.de \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.