Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org, Romain Naour <romain.naour@smile.fr>,
	Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Romain Naour <romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH] package/gcc: fortran support now requires MMU
Date: Sat, 15 Aug 2026 12:34:32 +0200	[thread overview]
Message-ID: <fc1a502f370e23dc0734c88ce0b32af8@free.fr> (raw)
In-Reply-To: <20260813131053.899334-1-thomas.petazzoni@bootlin.com>

On 13/08/2026 15:10, Thomas Petazzoni via buildroot wrote:
> Since upstream commit
> c66d1ba685b0d03b28967d2f7a48f6c64687efa2 ("Fortran: Add a shared
> memory multi process coarray implementation [PR88076]"), libgfortran
> now unconditionally uses fork(), which makes it impossible to build
> Fortran support on noMMU architectures.
> 
> In follow-up commit efb497c23a6f4109bf8794342617cbc161c08301, it was
> made even more clear: if you don't have fork() and you're not on
> WIN32:
> 
> +#else
> +#error "no way known to start child processes."
> +#endif
> 
> There are apparently no autobuilder failures for this issue, but the
> simple defconfig below allows to trigger the build failure:
> 
> BR2_arm=y
> BR2_cortex_m7=y
> BR2_GCC_VERSION_16_X=y
> BR2_TOOLCHAIN_BUILDROOT_FORTRAN=y
> 
> Even though this issue is only starting from GCC 16.x, we make Fortran
> unavailable on noMMU configurations regardless of the GCC version,
> with the reasoning that:
> 
> 1. Fortran on noMMU is unlikely to be in use
> 
> 2. Moving forward, all future versions of GCC will have this
>    restriction
> 
> Cc: Romain Naour <romain.naour@smile.fr>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-08-15 10:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-13 13:10 [Buildroot] [PATCH] package/gcc: fortran support now requires MMU Thomas Petazzoni via buildroot
2026-08-15 10:34 ` Julien Olivain 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=fc1a502f370e23dc0734c88ce0b32af8@free.fr \
    --to=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=ju.o@free.fr \
    --cc=romain.naour@gmail.com \
    --cc=romain.naour@smile.fr \
    --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