From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: Make gcc 6.0 or later a hard requirement now.
Date: Mon, 4 Dec 2017 12:02:20 -0700 [thread overview]
Message-ID: <a7ba29ee-006c-e265-a694-87eedcbb149b@wwwdotorg.org> (raw)
In-Reply-To: <1512263522-7584-1-git-send-email-trini@konsulko.com>
On 12/02/2017 06:12 PM, Tom Rini wrote:
> Move the warning to an error as we have been promising would happen in
> this release.
Oh. This has broken my U-Boot build/test system. I guess it's entirely
my fault for interpreting the "2018.01" warning as "you'll need to fix
this in Jan 2018", not "you'll need to fix this as soon as development
starts for 2018.01":-(
Is there a reason for requiring such an extremely new gcc, as opposed to
simply something not ancient? For example, no LTS version of Ubuntu
packages a compiler that's new enough to build U-Boot now:-(
next prev parent reply other threads:[~2017-12-04 19:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-03 1:12 [U-Boot] [PATCH] arm: Make gcc 6.0 or later a hard requirement now Tom Rini
2017-12-04 18:35 ` Tom Rini
2017-12-04 19:02 ` Stephen Warren [this message]
2017-12-04 19:09 ` Tom Rini
2017-12-05 6:53 ` Heiko Schocher
2017-12-05 11:44 ` Peter Robinson
2017-12-05 5:02 ` Heiko Schocher
2017-12-05 12:19 ` Tom Rini
2017-12-05 10:32 ` Dr. Philipp Tomsich
2017-12-05 17:02 ` Stephen Warren
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=a7ba29ee-006c-e265-a694-87eedcbb149b@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/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