From: ulf at uclibc.org <ulf@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot: toolchain
Date: Tue, 31 Jul 2007 15:38:52 -0700 (PDT) [thread overview]
Message-ID: <20070731223852.1C43FA458C@busybox.net> (raw)
Author: ulf
Date: 2007-07-31 15:38:52 -0700 (Tue, 31 Jul 2007)
New Revision: 19368
Log:
Change def of BR2_USE_WCHAR to build uClibc w WCHAR support
Modified:
trunk/buildroot/Config.in
trunk/buildroot/toolchain/Config.in.2
Changeset:
Modified: trunk/buildroot/Config.in
===================================================================
--- trunk/buildroot/Config.in 2007-07-31 18:40:17 UTC (rev 19367)
+++ trunk/buildroot/Config.in 2007-07-31 22:38:52 UTC (rev 19368)
@@ -651,12 +651,6 @@
help
This option hides outdated/obsolete versions of packages.
-config BR2_USE_WCHAR
- bool "Show packages that require WCHAR support"
- default y
- help
- This option hides packages which cannot be built without WCHAR.
-
choice
prompt "strip"
default BR2_STRIP_strip
Modified: trunk/buildroot/toolchain/Config.in.2
===================================================================
--- trunk/buildroot/toolchain/Config.in.2 2007-07-31 18:40:17 UTC (rev 19367)
+++ trunk/buildroot/toolchain/Config.in.2 2007-07-31 22:38:52 UTC (rev 19368)
@@ -41,6 +41,12 @@
help
Enable RPC. RPC support is needed for nfs.
+config BR2_USE_WCHAR
+ bool "Enable WCHAR support"
+ default n
+ help
+ Enable WCHAR. WCHAR support is needed for several packages
+
config BR2_SOFT_FLOAT
bool "Use software floating point by default"
default n
next reply other threads:[~2007-07-31 22:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 22:38 ulf at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-04 12:19 [Buildroot] svn commit: trunk/buildroot: toolchain jacmet 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=20070731223852.1C43FA458C@busybox.net \
--to=ulf@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