Hi,
On 10/13/23 03:03, Simon Richter wrote:
makes the problem reproducible even when building with -j2, and
regardless of whether building _all packages in the same build or not.
I'll check tomorrow about gcc 13 and if that also happens upstream.
gcc 13 is okay, because of 0bfc503c [1]. This patch does not apply
cleanly to gcc-12, because gm2 is a separate archive there, and the file
looks a bit different.
There are a few dependency rules in the file that seem to do the same
thing, but use the wrong target name, so they are ignored, and this
doesn't seem to be a complete set anyway. I'm trying with the same
addition of an order-only dependency that the gcc-13 commit does, if
that fixes it, that should be good enough for now.
Is the separate Modula2 tree still maintained? For us, the one-line fix
should probably be sufficient, but from an upstream perspective, this
should be looked at properly (but might be moot after the merge into
gcc-13).
Simon
[1]
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=00bfc503cc3b3e8f354afeac9b482649418fb70f
