From: zevv <uclibc@zevv.nl>
To: buildroot@busybox.net
Subject: [Buildroot] Changing uclibc runtime prefix
Date: Fri, 21 Dec 2007 04:19:05 -0800 (PST) [thread overview]
Message-ID: <14454607.post@talk.nabble.com> (raw)
Hello all,
I'm trying to deploy uClibc on a system with another C library on it, so
that I'll be able to run binaries linked to either one of the libc's.
I'd like to install uClibc in /usr/i386-uclibc/*, and configure the
cross-gcc and binutils to link against this library. I'm using buildroot to
generate the toolchain only.
Problem is that I can't get buildroot to configure uclibc and gcc the way I
want. My configuration
is as follows:
buildroot configuration (make menuconfig)
CONFIG_BR2_STAGING_DIR = /usr/i386-uclibc/
uclibc configuration (make uclibc-menuconfig)
CONFIG_SHARED_LIB_LOADER_PREFIX = /usr/i386-uclibc/lib
CONFIG_RUNTIME_PREFIX /usr/i386-uclibc/
The result is a uClibc and toolchain installed in /usr/i386-uclibc as
expected. The ld-library loader is installed in
/usr/i386-uclibc/lib/ld-uClibc.so.0 as well, just as it should.
The problem is that all binaries compiled with this toolchain, are still
expecting the ld library loader to be /lib/ld-uClibc.so.0, instead of
/usr/i386-uclibc/lib/ld-uClibc.so.0 !
My only conclusion is that I'm probably doing something wrong or have a
wrong understanding of what's happening here. Any tips on how to get this
working as described above ?
Thank you very much for your time,
Ico
--
View this message in context: http://www.nabble.com/Changing-uclibc-runtime-prefix-tp14454607p14454607.html
Sent from the BuildRoot mailing list archive at Nabble.com.
next reply other threads:[~2007-12-21 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-21 12:19 zevv [this message]
[not found] ` <200712211830.lBLIUfOI014955@orion.sysdev.org>
2007-12-21 19:03 ` [Buildroot] Changing uclibc runtime prefix Tony Borras
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=14454607.post@talk.nabble.com \
--to=uclibc@zevv.nl \
--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