From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/toolchain: binutils external-toolchain gcc uClibc
Date: Thu, 2 Apr 2009 11:56:13 +1100 [thread overview]
Message-ID: <20090402005613.GE29488@cloud.net.au> (raw)
In-Reply-To: <d6cda7730903311943o576aa1a9p932aecc9f5ada27f@mail.gmail.com>
On Tue, Mar 31, 2009 at 11:43:09PM -0300, Thiago A. Corr?a wrote:
> Hi,
>
> 2009/3/31 Thomas Petazzoni <thomas.petazzoni@free-electrons.com>:
> > Le Mon, 30 Mar 2009 16:56:54 -0300,
> > Thiago A. Corr?a <thiago.correa@gmail.com> a ?crit :
> >
> >> Would that be a bad thing? Even if it's not integrated but a script,
> >> say: ./script/fix-external-toolchain.sh
> >>
> >> Before/after running kconfig.
> >>
> >> It beats having the user to guess or remember.
> >
> > Or maybe we could just *not* show these options, and let a script
> > auto-detect the values. For uClibc, they can easily be guessed from
> > some uClibc-config.h script available in the toolchain.
>
> It must be "guessed" before entering kconfig because of the package
> options that depend on them. Specially large file support and IPv6.
Should those options (particularly large file support) just become
standard ie required?
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
prev parent reply other threads:[~2009-04-02 0:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 16:28 [Buildroot] svn commit: trunk/buildroot/toolchain: binutils external-toolchain gcc uClibc laird at uclibc.org
2009-03-30 13:32 ` Thomas Petazzoni
2009-03-30 13:46 ` Peter Korsgaard
2009-03-30 15:58 ` Thomas Petazzoni
2009-03-30 16:39 ` Thiago A. Corrêa
2009-03-30 18:58 ` Peter Korsgaard
2009-03-30 19:56 ` Thiago A. Corrêa
2009-03-31 23:28 ` Thomas Petazzoni
2009-04-01 2:43 ` Thiago A. Corrêa
2009-04-02 0:56 ` Hamish Moffatt [this message]
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=20090402005613.GE29488@cloud.net.au \
--to=hamish@cloud.net.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.