From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] package/Makefile.in: remove HOSTCC_VERSION
Date: Sun, 22 Nov 2015 22:43:58 +0100 [thread overview]
Message-ID: <87fuzx676p.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1448147919-5463-1-git-send-email-arnout@mind.be> (Arnout Vandecappelle's message of "Sun, 22 Nov 2015 00:18:37 +0100")
>>>>> "Arnout" == Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> writes:
> HOSTCC_VERSION is no longer used since gcc switched to the package
> infrastructure in e236fe481. It was in fact no longer needed since we
> dropped support for gcc 4.3.
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
> Note that we currently claim to support system gcc >= 2.95, but I don't
> think that matches reality...
Ehh, no. I guess a 4.x version would make more sense. Any idea what 'x'
should be? 3? 5? 7?
Committed to next, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2015-11-22 21:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-21 23:18 [Buildroot] [PATCH 1/3] package/Makefile.in: remove HOSTCC_VERSION Arnout Vandecappelle
2015-11-21 23:18 ` [Buildroot] [PATCH 2/3] Config.in: add symbols for BR2_HOST_GCC_AT_LEAST_X_Y Arnout Vandecappelle
2015-11-29 17:48 ` Yann E. MORIN
2015-11-29 20:55 ` Arnout Vandecappelle
2015-11-29 21:14 ` Yann E. MORIN
2015-11-29 21:41 ` Arnout Vandecappelle
2015-11-29 21:53 ` Yann E. MORIN
2015-11-21 23:18 ` [Buildroot] [PATCH 3/3] nodejs: version 4.X needs host GCC >= 4.8 Arnout Vandecappelle
2015-11-22 19:52 ` [Buildroot] [PATCH 1/3] package/Makefile.in: remove HOSTCC_VERSION Arnout Vandecappelle
2015-11-22 21:43 ` Peter Korsgaard [this message]
2015-11-23 19:50 ` Arnout Vandecappelle
2015-11-29 17:52 ` Thomas Petazzoni
2015-11-29 20:39 ` Peter Korsgaard
2015-11-29 20:45 ` Arnout Vandecappelle
2015-11-29 21:12 ` Peter Korsgaard
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=87fuzx676p.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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