From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/gcc: add support for gcc 8.1
Date: Sun, 20 May 2018 12:45:07 +0200 [thread overview]
Message-ID: <20180520124507.23c2a29b@windsurf> (raw)
In-Reply-To: <20180505105844.5278-1-romain.naour@gmail.com>
Hello Romain,
Thanks for working on this!
On Sat, 5 May 2018 12:58:44 +0200, Romain Naour wrote:
> Remove 0860-cilk-fix-build-without-wchar.patch since cilk has
> been removed from gcc.
>
> Rebase 0900-remove-selftests.patch on gcc 8.1.0
>
> Remove upstream patches 0001-m68k-coldfire-pr68467.patch and
> 0892-microblaze-Revert.patch.
>
> Use bz2 release tarball only for gcc 4.9 since all other version
> now use xz tarball.
>
> Runtime tested on x86_64 with binutils 2.30, gcc 8.1.0,
> kernel headers 4.14 and glibc 2.27.
>
> Buildtime tested with glibc with all supported architectures.
>
> Buildtime tested on x86_64 with musl and uClibc-ng
>
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> ---
> package/gcc/8.1.0/0001-uclibc-conf.patch | 29 ++++
> package/gcc/8.1.0/0002-arm-softfloat-libgcc.patch | 45 +++++++
> package/gcc/8.1.0/0003-remove-selftests.patch | 149 +++++++++++++++++++++
> package/gcc/Config.in.host | 7 +
> package/gcc/gcc.hash | 2 +
> package/gcc/gcc.mk | 10 +-
> toolchain/Config.in | 5 +
> .../toolchain-external-custom/Config.in.options | 6 +
Could you split up this patch in several patches:
- One adding the toolchain/Config.in contents for gcc 8.x
- One adding support for gcc 8.x in package/gcc
- One adding support for gcc 8.x in toolchain/toolchain-external
It would be good if you could also add a patch to update our default
gcc version to 7.x.
Maybe it's also time to remove gcc 4.9 and gcc 5.x ? I know when gcc
7.x was added and we changed to gcc 6.x as the default, we should have
removed gcc 4.9, but there was some opposition to this. Hopefully we
can do this removal now ?
> diff --git a/package/gcc/8.1.0/0001-uclibc-conf.patch b/package/gcc/8.1.0/0001-uclibc-conf.patch
> new file mode 100644
> index 0000000000..7d0f710945
> --- /dev/null
> +++ b/package/gcc/8.1.0/0001-uclibc-conf.patch
> @@ -0,0 +1,29 @@
> +From 07475e62626e246df07f35c4427b207c480b1f95 Mon Sep 17 00:00:00 2001
> +From: Romain Naour <romain.naour@gmail.com>
> +Date: Tue, 2 May 2017 22:36:15 +0200
> +Subject: [PATCH 1/3] uclibc-conf
Use "git format-patch -N" when generating patches to not have numbering
inside the patches.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-05-20 10:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-05 10:58 [Buildroot] [PATCH] package/gcc: add support for gcc 8.1 Romain Naour
2018-05-20 10:45 ` Thomas Petazzoni [this message]
2018-05-21 15:45 ` Romain Naour
2018-05-21 16:42 ` Romain Naour
2018-05-23 22:08 ` Arnout Vandecappelle
2018-07-30 13:09 ` Thomas Petazzoni
2018-05-21 21:52 ` Peter Korsgaard
2018-05-22 7:02 ` Thomas Petazzoni
2018-05-22 7:18 ` daggs
2018-05-22 7:46 ` Peter Korsgaard
2018-05-22 8:16 ` Thomas Petazzoni
2018-05-22 22:08 ` Arnout Vandecappelle
2018-05-23 20:19 ` Romain Naour
2018-05-23 21:34 ` Arnout Vandecappelle
2018-05-22 7:13 ` daggs
2018-05-23 8:29 ` Thomas Petazzoni
2018-05-23 20:23 ` Romain Naour
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=20180520124507.23c2a29b@windsurf \
--to=thomas.petazzoni@bootlin.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