From: aldot at uclibc.org <aldot@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/toolchain
Date: Wed, 24 Jan 2007 06:50:22 -0800 (PST) [thread overview]
Message-ID: <20070124145022.3B89C48598@busybox.net> (raw)
Author: aldot
Date: 2007-01-24 06:50:21 -0800 (Wed, 24 Jan 2007)
New Revision: 17498
Log:
- reformat help text to fit default width better
Modified:
trunk/buildroot/toolchain/Config.in
Changeset:
Modified: trunk/buildroot/toolchain/Config.in
===================================================================
--- trunk/buildroot/toolchain/Config.in 2007-01-24 14:49:49 UTC (rev 17497)
+++ trunk/buildroot/toolchain/Config.in 2007-01-24 14:50:21 UTC (rev 17498)
@@ -36,11 +36,15 @@
help
If your target CPU does not have a Floating Point Unit (FPU) or a
kernel FPU emulator, but you still wish to support floating point
- functions, then everything will need to be compiled with soft floating
- point support (-msoft-float).
+ functions, then everything will need to be compiled with soft
+ floating point support (-msoft-float).
Most people will answer N.
+#config BR2_SOFT_FLOAT_FP
+# bool "Use softfp"
+# default n
+
config BR2_TARGET_OPTIMIZATION
string "Target Optimizations"
default "-Os -pipe"
@@ -51,12 +55,13 @@
bool "Include target utils in cross toolchain"
default y
help
- When using buildroot to build a deployable cross toolchain, it is handy
- to include certain target apps with that toolchain as a convenience.
+ When using buildroot to build a deployable cross toolchain,
+ it is handy to include certain target apps with that toolchain
+ as a convenience.
Examples include ldd, gdbserver, and strace.
- Answer Y if you want these apps (if built) copied into the cross toolchain
- dir under <arch>-linux-uclibc/target_utils/.
+ Answer Y if you want these apps (if built) copied into the
+ cross toolchain dir under <arch>-linux-uclibc/target_utils/.
endmenu
next reply other threads:[~2007-01-24 14:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 14:50 aldot at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-02 20:31 [Buildroot] svn commit: trunk/buildroot/toolchain jacmet at uclibc.org
2008-12-23 10:21 jacmet at uclibc.org
2008-06-16 7:15 jacmet at uclibc.org
2008-03-29 23:10 ulf at uclibc.org
2008-03-30 13:03 ` Peter Korsgaard
2008-03-30 23:39 ` Hamish Moffatt
2008-03-31 6:49 ` Peter Korsgaard
2008-03-29 11:04 ulf at uclibc.org
2008-03-13 17:10 ninevoltz at uclibc.org
2008-03-13 18:23 ` Peter Korsgaard
2008-03-13 18:28 ` John Voltz
2008-03-13 19:35 ` Peter Korsgaard
2008-03-13 20:39 ` John Voltz
2007-10-05 11:02 aldot at uclibc.org
2007-09-28 19:56 ulf at uclibc.org
2007-09-25 22:03 aldot at uclibc.org
2007-09-25 21:49 aldot at uclibc.org
2007-08-21 19:45 aldot at uclibc.org
2007-07-07 9:31 aldot at uclibc.org
2007-06-20 12:00 aldot at uclibc.org
2007-03-21 10:55 aldot at uclibc.org
2007-01-21 11:34 aldot 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=20070124145022.3B89C48598@busybox.net \
--to=aldot@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