public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/103574] New: race condition in bootstrap build, trunk 20211203
Date: Mon, 06 Dec 2021 09:43:43 +0000 [thread overview]
Message-ID: <bug-103574-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103574
Bug ID: 103574
Summary: race condition in bootstrap build, trunk 20211203
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: modula2
Assignee: unassigned at gcc dot gnu.org
Reporter: doko at debian dot org
Target Milestone: ---
there seems to be a race condition with a normal bootstrap build, at least on
sme architectures, here on sparc64-linux-gnu:
/usr/bin/sparc64-linux-gnu-ld: cannot find libcommon.a: No such file or
directory
collect2: error: ld returned 1 exit status
make[5]: *** [../../src/gcc/m2/Make-lang.in:1804: stage1/m2/gm2m] Error 1
make[5]: *** Waiting for unfinished jobs....
rm gpl.pod gcc.pod gfdl.pod lto-dump.pod gdc.pod gfortran.pod
make[5]: Leaving directory '/<<PKGBUILDDIR>>/build/gcc'
make[4]: *** [Makefile:5047: all-stage3-gcc] Error 2
make[4]: Leaving directory '/<<PKGBUILDDIR>>/build'
make[3]: *** [Makefile:27484: stage3-bubble] Error 2
make[3]: Leaving directory '/<<PKGBUILDDIR>>/build'
make[2]: *** [Makefile:27548: bootstrap] Error 2
make[2]: Leaving directory '/<<PKGBUILDDIR>>/build'
next reply other threads:[~2021-12-06 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 9:43 doko at debian dot org [this message]
2022-11-04 11:22 ` [Bug modula2/103574] " doko at gcc dot gnu.org
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=bug-103574-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).