From: Robert Urban <urban@unix-beratung.de>
To: buildroot@busybox.net
Subject: [Buildroot] how to get compilation environment right?
Date: Sun, 22 Mar 2009 00:21:19 +0100 [thread overview]
Message-ID: <49C5766F.3050207@unix-beratung.de> (raw)
Hi Folks,
I'm trying to build cpufrequtils-005, which doesn't use configure. Instead
it has a simple makefile:
http://www.spielwiese.de/rob/Buildroot/Makefile
which uses libtool to compile library objects as follows:
$(LIBTOOL) $(LIBTOOL_OPT) --mode=compile \
$(CC) $(CFLAGDEF) $(CFLAGS) -o $@ -c $*.c
the library gets built without errors, but when make tries to link a utility
which uses the library, I see complaints about undefined symbols in the form
of "function at GLIBC_2.0", and that "libc.so.6" (which is the host libc) is
needed, but not found.
If I compare a gcc line from cpufrequtils to something sucessful, I notice
that the gcc flags "-sysroot" and "-isysroot" are not present, which would
seem to explain why the host libc is being linked against.
What is the proper method of sorting out such problems?
thanks,
Rob Urban
P.S. the buildroot config I'm using can be seen here:
http://www.spielwiese.de/rob/Buildroot/config
reply other threads:[~2009-03-21 23:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=49C5766F.3050207@unix-beratung.de \
--to=urban@unix-beratung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox