From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 next 1/7] toolchain: add common binutils version hidden config options
Date: Wed, 8 Jun 2016 23:21:06 +0200 [thread overview]
Message-ID: <20160608232106.2c24920e@free-electrons.com> (raw)
In-Reply-To: <1464693078-15767-1-git-send-email-Vincent.Riera@imgtec.com>
Hello,
On Tue, 31 May 2016 12:11:12 +0100, Vicente Olivert Riera wrote:
> This commit adds a number of hidden Config.in options, that will be used
> to handle dependencies on the binutils version. We mimic the model that
> was used for the kernel headers dependency mechanism.
>
> These hidden options will be selected by the internal and external
> toolchain backend logic respectively, in follow-up commits.
>
> These options will be helpful when we need to make packages depend on
> certain version of binutils. Further patches will do this for gcc and
> valgrind packages.
>
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
I was about to apply this series, but in fact, I'm going to reject it,
as I believe the annoyance / benefit ratio is not good.
You are introducing those binutils version selectors to solve two
problems:
* The fact that gcc 4.8 does not work on MIPS with binutils >= 2.25.
binutils 2.25 is already our default, and as soon as binutils 2.27
is released, 2.26 will be the default, and 2.24 will be removed,
leaving in fact no way to select gcc 4.8 on MIPS.
So I would prefer that we simply disallow gcc 4.8 on MIPS completely.
* The fact that Valgrind doesn't work on MIPS soft-float with binutils
>= 2.25. Same comment here: just disable Valgrind on MIPS soft-float
and that's it.
Normally, the version option are used to indicate that something
*works* only after a certain version (like kernel headers >= 3.10, or
gcc >= 4.9).
But here, you're using the options in the opposite way: to say that
anything after binutils 2.25 (included) is broken. With 2.24 going away
in the near future, I rather prefer the above solutions that to add
those additional binutils version options.
So could you instead submit patches that:
1/ Disallow gcc 4.8 on MIPS
2/ Disallow valgrind on MIPS soft-float
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-06-08 21:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 11:11 [Buildroot] [PATCH v2 next 1/7] toolchain: add common binutils version hidden config options Vicente Olivert Riera
2016-05-31 11:11 ` [Buildroot] [PATCH v2 next 2/7] toolchain-external: add support for binutils version dependency Vicente Olivert Riera
2016-05-31 11:11 ` [Buildroot] [PATCH v2 next 3/7] binutils: handle ARC more atomically Vicente Olivert Riera
2016-06-07 21:13 ` Yann E. MORIN
2016-05-31 11:11 ` [Buildroot] [PATCH v2 next 4/7] binutils: select the appropriate BR2_TOOLCHAIN_BINUTILS_AT_LEAST_X_Y Vicente Olivert Riera
2016-06-07 21:15 ` Yann E. MORIN
2016-05-31 11:11 ` [Buildroot] [PATCH v2 next 5/7] docs: add documentation for BR2_TOOLCHAIN_BINUTILS_AT_LEAST Vicente Olivert Riera
2016-05-31 11:13 ` [Buildroot] [PATCH v2 next 6/7] Disable gcc-4.8 + binutils >= 2.25 + MIPS combination Vicente Olivert Riera
2016-05-31 11:13 ` [Buildroot] [PATCH v2 next 7/7] valgrind: disable for MIPS soft-float when using binutils >= 2.25 Vicente Olivert Riera
2016-06-07 21:38 ` Yann E. MORIN
2016-06-07 21:23 ` [Buildroot] [PATCH v2 next 6/7] Disable gcc-4.8 + binutils >= 2.25 + MIPS combination Yann E. MORIN
2016-06-08 21:21 ` Thomas Petazzoni [this message]
2016-06-17 11:54 ` [Buildroot] [PATCH v2 next 1/7] toolchain: add common binutils version hidden config options Vicente Olivert Riera
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=20160608232106.2c24920e@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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