All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/6] Move BR2_SOFT_FLOAT and BR2_VFP_FLOAT to Build options
Date: Thu, 28 Jan 2010 17:26:27 +0100	[thread overview]
Message-ID: <871vhanqks.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <dec9e118437c50f39437596da1717c5117b8d416.1263338839.git.thomas.petazzoni@free-electrons.com> (Thomas Petazzoni's message of "Wed, 13 Jan 2010 00:27:22 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 Thomas> The soft floating point related options not only affect how the
 Thomas> toolchain is built, but more importantly affect how packages are
 Thomas> built. Therefore, just like optimization or stripping options,
 Thomas> floating point related options are global, and belong to the Build
 Thomas> options menu.

Hmm, couldn't you say the same for ipv6, largefile and locale stuff?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2010-01-28 16:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-12 23:27 [Buildroot] [pull request] Pull request for branch toolchain-config-improvements Thomas Petazzoni
2010-01-12 23:27 ` [Buildroot] [PATCH 1/6] Move locale purge option to a more logical location Thomas Petazzoni
2010-01-12 23:27 ` [Buildroot] [PATCH 2/6] lzma: Use BR2_INSTALL_LIBSTDCPP instead of BR2_GCC_CROSS_CXX like in other packages Thomas Petazzoni
2010-01-12 23:27 ` [Buildroot] [PATCH 3/6] Move BR2_SOFT_FLOAT and BR2_VFP_FLOAT to Build options Thomas Petazzoni
2010-01-28 16:26   ` Peter Korsgaard [this message]
2010-02-09 21:02     ` Thomas Petazzoni
2010-01-12 23:27 ` [Buildroot] [PATCH 4/6] Move BR2_TARGET_OPTIMIZATION to Build Options and rename it Thomas Petazzoni
2010-01-12 23:27 ` [Buildroot] [PATCH 5/6] Update defconfigs after BR2_TARGET_OPTIMIZATION rename Thomas Petazzoni
2010-01-12 23:27 ` [Buildroot] [PATCH 6/6] toolchain: Clarify configuration option files organization Thomas Petazzoni

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=871vhanqks.fsf@macbook.be.48ers.dk \
    --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 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.