From: jacmet at uclibc.org <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/toolchain/external-toolchain
Date: Mon, 16 Jun 2008 05:22:46 -0700 (PDT) [thread overview]
Message-ID: <20080616122246.C821B3C987@busybox.net> (raw)
Author: jacmet
Date: 2008-06-16 05:22:45 -0700 (Mon, 16 Jun 2008)
New Revision: 22378
Log:
toolchain: more sensible uclibc defaults for external toolchain
Modified:
trunk/buildroot/toolchain/external-toolchain/Config.in
Changeset:
Modified: trunk/buildroot/toolchain/external-toolchain/Config.in
===================================================================
--- trunk/buildroot/toolchain/external-toolchain/Config.in 2008-06-16 11:42:19 UTC (rev 22377)
+++ trunk/buildroot/toolchain/external-toolchain/Config.in 2008-06-16 12:22:45 UTC (rev 22378)
@@ -6,7 +6,7 @@
config BR2_TOOLCHAIN_EXTERNAL_LIB_C
string "The core C library from the external toolchain"
- default "libc.so.6"
+ default "libc.so.0"
help
Specify the core C shared library found in the external
toolchain. This is required in addition to any other
@@ -14,7 +14,7 @@
config BR2_TOOLCHAIN_EXTERNAL_LIBS
string "Libraries to copy from the external toolchain"
- default ""
+ default "ld-uClibc.so.0 libcrypt.so.0 libdl.so.0 libgcc_s.so libm.so.0 libnsl.so.0 libpthread.so.0 libresolv.so.0 librt.so.0 libutil.so.0"
help
A space separated list of the shared libraries to be copied
from the external toolchain into the root filesystem. Only
@@ -34,13 +34,13 @@
config BR2_TOOLCHAIN_EXTERNAL_PATH
string "External toolchain path"
- default ""
+ default "/path/to/staging_dir/usr"
help
Path to where the external toolchain is installed.
config BR2_TOOLCHAIN_EXTERNAL_PREFIX
string "External toolchain prefix"
- default ""
+ default "$(ARCH)-linux"
help
This the the external toolchain prefix. For example:
armeb-unknown-linux-gnu, mipsel-unknown-linux-gnu, etc.
next reply other threads:[~2008-06-16 12:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 12:22 jacmet at uclibc.org [this message]
2008-06-16 13:54 ` [Buildroot] svn commit: trunk/buildroot/toolchain/external-toolchain Bernhard Fischer
2008-06-16 14:07 ` Peter Korsgaard
2008-06-16 15:35 ` Bernhard Fischer
2008-06-17 4:23 ` Hamish Moffatt
2008-06-17 7:16 ` Peter Korsgaard
2008-06-17 10:47 ` Hamish Moffatt
2008-06-17 13:45 ` Peter Korsgaard
2008-06-17 14:29 ` Bernhard Fischer
2008-06-17 14:55 ` Peter Korsgaard
2008-06-17 15:45 ` Bernhard Fischer
2008-06-18 1:18 ` Hamish Moffatt
2008-06-18 5:03 ` [Buildroot] svncommit: trunk/buildroot/toolchain/external-toolchain Ulf Samuelsson
2008-06-18 7:36 ` [Buildroot] svn commit: trunk/buildroot/toolchain/external-toolchain Peter Korsgaard
2008-06-18 1:05 ` Hamish Moffatt
-- strict thread matches above, loose matches on Subject: below --
2009-01-12 12:54 laird at uclibc.org
2008-11-03 10:37 jacmet at uclibc.org
2008-11-03 10:32 jacmet at uclibc.org
2008-10-17 10:19 jacmet at uclibc.org
2007-07-17 0:18 sjhill at uclibc.org
2007-04-28 17:10 sjhill at uclibc.org
2007-04-19 2:04 sjhill at uclibc.org
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=20080616122246.C821B3C987@busybox.net \
--to=jacmet@uclibc.org \
--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