From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Romain Naour <romain.naour@gmail.com>
Cc: Eric Le Bihan <eric.le.bihan.dev@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/gcc: disable gcc D front-end with gcc 12
Date: Tue, 23 Aug 2022 22:21:58 +0200 [thread overview]
Message-ID: <20220823222158.7a302f45@windsurf> (raw)
In-Reply-To: <20220821152749.239482-1-romain.naour@gmail.com>
On Sun, 21 Aug 2022 17:27:49 +0200
Romain Naour <romain.naour@gmail.com> wrote:
> "The D front-end is now itself written in D, in order to build GDC, you
> will need a working GDC compiler (GCC version 9.1 or later)." [1]
>
> So we have to check if a D compiler is available on the host.
>
> Fixes:
> http://autobuild.buildroot.org/results/36a/36aa22e458d53ab8687b3a79ffeb65b18e8ac6e7/host-gcc-final-12.1.0/build
>
> [1] https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=5fee5ec362f7a243f459e6378fd49dfc89dc9fb5
>
> http://lists.busybox.net/pipermail/buildroot/2022-August/648841.html
>
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> Cc: Eric Le Bihan <eric.le.bihan.dev@free.fr>
> ---
> package/gcc/Config.in.host | 4 ++++
> 1 file changed, 4 insertions(+)
Applied to master, thanks. Unless someone steps up to fix the support
for the D language, it means that ultimately we would drop support for
it.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-08-23 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 15:27 [Buildroot] [PATCH] package/gcc: disable gcc D front-end with gcc 12 Romain Naour
2022-08-23 20:21 ` Thomas Petazzoni via buildroot [this message]
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=20220823222158.7a302f45@windsurf \
--to=buildroot@buildroot.org \
--cc=eric.le.bihan.dev@free.fr \
--cc=romain.naour@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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