From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/4] Supply better default uClibc config file when using ct-ng
Date: Wed, 14 Dec 2011 07:51:38 +0100 [thread overview]
Message-ID: <201112140751.38731.arnout@mind.be> (raw)
In-Reply-To: <1323173840-8837-3-git-send-email-will_wagner@carallon.com>
On Tuesday 06 December 2011 13:17:18 Will Wagner wrote:
> +config BR2_TOOLCHAIN_CTNG_uClibc_CONFIG
> + default "toolchain/uClibc/uClibc-0.9.30.config" if BR2_TOOLCHAIN_CTNG_uClibc_VERSION_0_9_30
> + default "toolchain/uClibc/uClibc-0.9.32.config" if BR2_TOOLCHAIN_CTNG_uClibc_VERSION_0_9_32
> +
I believe that if you don't specify a type, it will default to bool.
So you should add a line containing only 'string'.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 31BB CF53 8660 6F88 345D 54CC A836 5879 20D7 CF43
next prev parent reply other threads:[~2011-12-14 6:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 12:17 [Buildroot] [PATCH v2 0/4] Improved uClibc support with ct-ng generated toolchain Will Wagner
2011-12-06 12:17 ` [Buildroot] [PATCH v2 1/4] Allow user to pick uClibc version when using ct-ng Will Wagner
2011-12-14 6:54 ` Arnout Vandecappelle
2011-12-06 12:17 ` [Buildroot] [PATCH v2 2/4] Supply better default uClibc config file " Will Wagner
2011-12-14 6:51 ` Arnout Vandecappelle [this message]
2011-12-06 12:17 ` [Buildroot] [PATCH v2 3/4] Allow user to specify a custom " Will Wagner
2011-12-06 12:17 ` [Buildroot] [PATCH v2 4/4] Allow user to select nptl when using 0.9.32 with ct-ng Will Wagner
2011-12-14 6:56 ` [Buildroot] [PATCH v2 0/4] Improved uClibc support with ct-ng generated toolchain Arnout Vandecappelle
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=201112140751.38731.arnout@mind.be \
--to=arnout@mind.be \
--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