From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] External toolchain improvements
Date: Tue, 14 Jul 2009 16:41:09 +0200 [thread overview]
Message-ID: <20090714164109.26df9c81@surf> (raw)
In-Reply-To: <1247513162.8439.10.camel@coalu.atr>
Hello Lionel,
Le Mon, 13 Jul 2009 21:26:02 +0200,
Lionel Landwerlin <lionel.landwerlin@openwide.fr> a ?crit :
> Just a word about the choice to put the EXTERNAL_LIBS variable in
> toolchain/external-toolchain/ext-tool.mk. I don't think it's a good
> choice. For example, my current toolchain includes a glibc version
> 2.6. This make the ld-linux loader name /lib/ld-linux.so.2 instead
> of /lib/ld-linux.so.3.
>
> Modifying an enormous variable inside kconfig is painful, but I think
> it's better to let this variable configurable rather than encourage
> the buildroot user to modify an unfriendly makefile
> (toolchain/external-toolchain/ext-tool.mk).
This is also something I've discovered recently. I'd like to spend some
time to see if it's still possible to auto-detect the version of the
libraries to copy. If it doesn't work, then I fallback to the previous
solution, which I don't find really nice.
Sincerly,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2009-07-14 14:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.0.1246405094.1110.buildroot@busybox.net>
2009-06-30 23:50 ` [Buildroot] External toolchain improvements Lionel Landwerlin
2009-06-30 23:54 ` Lionel Landwerlin
2009-07-01 14:05 ` Thomas Petazzoni
2009-07-01 21:43 ` Lionel Landwerlin
2009-07-02 12:50 ` Thomas Petazzoni
2009-07-03 6:01 ` Lionel Landwerlin
2009-07-03 8:13 ` Thomas Petazzoni
2009-07-03 21:24 ` Lionel Landwerlin
2009-07-06 0:51 ` Lionel Landwerlin
2009-07-13 19:26 ` Lionel Landwerlin
2009-07-14 14:41 ` Thomas Petazzoni [this message]
2009-07-14 19:51 ` Lionel Landwerlin
2009-06-01 16:54 Thomas Petazzoni
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=20090714164109.26df9c81@surf \
--to=thomas.petazzoni@free-electrons.com \
--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