public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/103306] New: parallel build hangs since 04c5a91d068c4ca2f09c2bc206fce00db9d1790b Date: Wed, 17 Nov 2021 19:14:34 +0000 [thread overview] Message-ID: <bug-103306-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103306 Bug ID: 103306 Summary: parallel build hangs since 04c5a91d068c4ca2f09c2bc206fce00db9d1790b Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: build Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: zsojka at seznam dot cz Target Milestone: --- Host: x86_64-pc-linux-gnu Target: x86_64-pc-linux-gnu Build: x86_64-pc-linux-gnu For a few days, I am failing to build a x86_64-pc-linux-gnu compiler on one of my systems; both bootstrap and non-bootstrap builds behave the same. libtool: link: x86_64-pc-linux-gnu-ranlib .libs/libubsan.a libtool: link: rm -fr .libs/libubsan.lax libtool: link: ( cd ".libs" && rm -f "libubsan.la" && ln -s "../libubsan.la" "libubsan.la" ) make[8]: Leaving directory '/repo/build-gcc-trunk-amd64/x86_64-pc-linux-gnu/32/libsanitizer/ubsan' make[8]: Entering directory '/repo/build-gcc-trunk-amd64/x86_64-pc-linux-gnu/32/libsanitizer' true "AR_FLAGS=rc" "CC_FOR_BUILD=x86_64-pc-linux-gnu-gcc" "CFLAGS=-g -O2 -m32" "CXXFLAGS=-g -O2 -D_GNU_SOURCE -m32" "CFLAGS_FOR_BUILD=-g -O2" "CFLAGS_FOR_TARGET=-g -O2" "INSTALL=/usr/bin/install -c" "INSTALL_DATA=/usr/bin/install -c -m 644" "INSTALL_PROGRAM=/usr/bin/install -c" "INSTALL_SCRIPT=/usr/bin/install -c" "JC1FLAGS=" "LDFLAGS=-m32" "LIBCFLAGS=-g -O2 -m32" "LIBCFLAGS_FOR_TARGET=-g -O2" "MAKE=make" "MAKEINFO=makeinfo --split-size=5000000 " "PICFLAG=" "PICFLAG_FOR_TARGET=" "SHELL=/bin/sh" "RUNTESTFLAGS=" "exec_prefix=/repo/gcc-trunk//binary-trunk-r12-5339-20211114023225-g04c5a91d068-checking-yes-rtl-df-extra-nobootstrap-amd64" "infodir=/repo/gcc-trunk//binary-trunk-r12-5339-20211114023225-g04c5a91d068-checking-yes-rtl-df-extra-nobootstrap-amd64/share/info" "libdir=/repo/gcc-trunk//binary-trunk-r12-5339-20211114023225-g04c5a91d068-checking-yes-rtl-df-extra-nobootstrap-amd64/lib" "prefix=/repo/gcc-trunk//binary-trunk-r12-5339-20211114023225-g04c5a91d068-checking-yes-rtl-df-extra-nobootstrap-amd64" "includedir=/repo/gcc-trunk//binary-trunk-r12-5339-20211114023225-g04c5a91d068-checking-yes-rtl-df-extra-nobootstrap-amd64/include" "AR=x86_64-pc-linux-gnu-ar" "AS=/repo/build-gcc-trunk-amd64/./gcc/as" "LD=/repo/build-gcc-trunk-amd64/./gcc/collect-ld -m elf_x86_64 -m elf_i386" "LIBCFLAGS=-g -O2 -m32" "NM=/repo/build-gcc-trunk-amd64/./gcc/nm" "PICFLAG=" "RANLIB=x86_64-pc-linux-gnu-ranlib" "DESTDIR=" DO=all multi-do # make make[8]: Leaving directory '/repo/build-gcc-trunk-amd64/x86_64-pc-linux-gnu/32/libsanitizer' make[7]: Leaving directory '/repo/build-gcc-trunk-amd64/x86_64-pc-linux-gnu/32/libsanitizer' make[6]: Leaving directory '/repo/build-gcc-trunk-amd64/x86_64-pc-linux-gnu/32/libsanitizer' make[5]: Leaving directory '/repo/build-gcc-trunk-amd64/x86_64-pc-linux-gnu/libsanitizer' make[4]: Leaving directory '/repo/build-gcc-trunk-amd64/x86_64-pc-linux-gnu/libsanitizer' make[3]: Leaving directory '/repo/build-gcc-trunk-amd64/x86_64-pc-linux-gnu/libsanitizer' make[2]: Leaving directory '/repo/build-gcc-trunk-amd64/x86_64-pc-linux-gnu/libsanitizer' make[1]: Leaving directory '/repo/build-gcc-trunk-amd64' The system is 100% idle afterwards, but I don't get my terminal / build script doesn't continue with make install. I've bisected this to have started with 04c5a91d068c4ca2f09c2bc206fce00db9d1790b Configure: /repo/gcc-trunk//configure --enable-languages=c,c++ --enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra --disable-bootstrap --with-cloog --with-ppl --with-isl --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu --with-ld=/usr/bin/x86_64-pc-linux-gnu-ld --with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch --prefix=/repo/gcc-trunk//binary-trunk-r12-5339-20211114023225-g04c5a91d068-checking-yes-rtl-df-extra-nobootstrap-amd64 make: make -j8 non-parallel build works fine: make -j1
next reply other threads:[~2021-11-17 19:14 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-17 19:14 zsojka at seznam dot cz [this message] 2021-11-17 20:18 ` [Bug bootstrap/103306] parallel build hangs since r12-5234-g04c5a91d068c4ca2f09c2bc206fce00db9d1790b pinskia at gcc dot gnu.org 2021-11-17 20:22 ` pinskia at gcc dot gnu.org 2021-11-17 21:14 ` zsojka at seznam dot cz 2021-11-17 23:06 ` pinskia at gcc dot gnu.org 2021-11-18 6:36 ` zsojka at seznam dot cz 2021-11-18 7:49 ` zsojka at seznam dot cz 2021-11-18 7:53 ` rguenth at gcc dot gnu.org 2021-11-18 7:57 ` jakub at gcc dot gnu.org 2021-11-18 8:01 ` pinskia at gcc dot gnu.org 2021-11-18 8:03 ` zsojka at seznam dot cz 2021-11-18 8:07 ` pinskia at gcc dot gnu.org 2021-11-18 8:07 ` [Bug bootstrap/103306] [12 Regression] parallel build hangs since r12-5234-g04c5a9 when /usr/include includes broken symbolic links pinskia at gcc dot gnu.org 2021-11-18 8:10 ` zsojka at seznam dot cz 2021-11-18 10:22 ` xry111 at mengyan1223 dot wang 2021-11-18 10:23 ` zsojka at seznam dot cz 2021-11-18 10:39 ` jakub at gcc dot gnu.org 2021-11-18 11:02 ` xry111 at mengyan1223 dot wang 2021-11-19 4:56 ` zsojka at seznam dot cz 2021-11-20 13:18 ` xry111 at mengyan1223 dot wang 2021-11-23 19:20 ` cvs-commit at gcc dot gnu.org 2021-11-23 19:21 ` xry111 at mengyan1223 dot wang 2021-11-28 1:27 ` pinskia 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-103306-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: linkBe 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).