From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/9] toolchain-external: add support for gcc version dependency
Date: Wed, 12 Aug 2015 10:30:16 +0200 [thread overview]
Message-ID: <20150812103016.6f8ec2fd@free-electrons.com> (raw)
In-Reply-To: <979955045.8284402.1439295583830.JavaMail.zimbra@datacom.ind.br>
Dear Carlos Santos,
On Tue, 11 Aug 2015 09:19:43 -0300 (BRT), Carlos Santos wrote:
> The problem goes away if I add BR2_TOOLCHAIN_EXTERNAL_GCC_4_8=y to my
> custom defconfig. It was missing in the original file but the absence
> was harmless.
>
> Anyone using an external toolchain will face the same problem, so I
> think it's important to emphasize the consequences of the change in
> the release notes.
There is no need for that, the error message tells you that the
selection of the gcc version is incorrect. It is exactly the same sort
of checks that is used to validate the selected C library, etc.
The mechanism to specify the gcc version has been added very recently,
so that's why you're seeing the problem now.
If you hand-edit your defconfig, you're supposed to know what you're
doing. Otherwise, 'make menuconfig' will show an option to select the
gcc version used in your external toolchain.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-08-12 8:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 18:00 [Buildroot] [PATCH 0/9] Add gcc version dependency mechanism Thomas Petazzoni
2015-08-04 18:00 ` [Buildroot] [PATCH 1/9] toolchain: add common gcc version hidden config options Thomas Petazzoni
2015-08-04 19:12 ` Yann E. MORIN
2015-08-04 18:00 ` [Buildroot] [PATCH 2/9] gcc: select the appropriate BR2_TOOLCHAIN_GCC_AT_LEAST_* option Thomas Petazzoni
2015-08-04 19:14 ` Yann E. MORIN
2015-08-04 18:00 ` [Buildroot] [PATCH 3/9] toolchain-external: add support for gcc version dependency Thomas Petazzoni
2015-08-04 19:49 ` Yann E. MORIN
2015-08-05 10:14 ` Thomas Petazzoni
2015-08-08 12:23 ` Jörg Krause
2015-08-08 12:33 ` Thomas Petazzoni
[not found] ` <1485266737.8272514.1439293774884.JavaMail.zimbra@datacom.ind.br>
[not found] ` <979955045.8284402.1439295583830.JavaMail.zimbra@datacom.ind.br>
2015-08-12 8:30 ` Thomas Petazzoni [this message]
2015-08-04 18:00 ` [Buildroot] [PATCH 4/9] docs/manual: document gcc version dependencies Thomas Petazzoni
2015-08-04 19:58 ` Yann E. MORIN
2015-08-05 9:05 ` Thomas Petazzoni
2015-08-05 19:53 ` Yann E. MORIN
2015-08-04 18:00 ` [Buildroot] [PATCH 5/9] libsigrok: depends on gcc >= 4.7 Thomas Petazzoni
2015-08-04 20:08 ` Yann E. MORIN
2015-08-05 7:56 ` Thomas Petazzoni
2015-08-04 18:00 ` [Buildroot] [PATCH 6/9] upmpdcli: update to use the gcc version dependency mechanism Thomas Petazzoni
2015-08-04 20:11 ` Yann E. MORIN
2015-08-04 18:00 ` [Buildroot] [PATCH 7/9] zmqpp: " Thomas Petazzoni
2015-08-04 20:12 ` Yann E. MORIN
2015-08-05 10:15 ` Thomas Petazzoni
2015-08-04 18:00 ` [Buildroot] [PATCH 8/9] libupnpp: " Thomas Petazzoni
2015-08-04 20:21 ` Yann E. MORIN
2015-08-04 18:00 ` [Buildroot] [PATCH 9/9] mpd: " Thomas Petazzoni
2015-08-04 20:22 ` Yann E. MORIN
2015-08-05 10:13 ` [Buildroot] [PATCH 0/9] Add " 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=20150812103016.6f8ec2fd@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