public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dilyan.palauzov at aegee dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/106472] No rule to make target '../libbacktrace/libbacktrace.la', needed by 'libgo.la'. Date: Wed, 26 Jul 2023 18:11:05 +0000 [thread overview] Message-ID: <bug-106472-4-j1GiHv7IlX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106472-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106472 Дилян Палаузов <dilyan.palauzov at aegee dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dilyan.palauzov at aegee dot org --- Comment #27 from Дилян Палаузов <dilyan.palauzov at aegee dot org> --- With gcc 13 at commit 670caa3f043e6a7af72bd76482a79a703a652ee5 (origin/releases/gcc-13) Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Tue Jul 25 00:23:26 2023 +0000 Daily bump. after calling export CONFIG_SITE="a" mkdir -p build && cd build && ../configure --enable-threads=posix --enable-nls --disable-multilib --enable-interpreter --with-system-zlib --enable-languages=c,c++,go,lto --enable-targets=all --with-system-unwind --without-x --with-linker-hash-style=gnu --enable-shared --with-build-config=bootstrap-lto\ bootstrap-O3 &> ../c-out && make build fails at stage 3 with libtool: compile: /git/gcc/build/./gcc/xgcc -B/git/gcc/build/./gcc/ -B/usr/local/x86_64-pc-linux-gnu/bin/ -B/usr/local/x86_64-pc-linux-gnu/lib/ -isystem /usr/local/x86_64-pc-linux-gnu/include -isystem /usr/local/x86_64-pc-linux-gnu/sys-include -DHAVE_CONFIG_H -I. -I../../../libgo -I ../../../libgo/runtime -I../../../libgo/../libffi/include -I../libffi/include -pthread -L../libatomic/.libs -fexceptions -fnon-call-exceptions -fsplit-stack -Wall -Wextra -Wwrite-strings -Wcast-qual -Werror -minline-all-stringops -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I ../../../libgo/../libgcc -I ../../../libgo/../libbacktrace -I ../../gcc/include -g -O2 -c ../../../libgo/go/golang.org/x/sys/cpu/cpu_gccgo_x86.c -fPIC -DPIC -o golang.org/x/sys/.libs/cpu_gccgo_x86.o libtool: compile: /git/gcc/build/./gcc/xgcc -B/git/gcc/build/./gcc/ -B/usr/local/x86_64-pc-linux-gnu/bin/ -B/usr/local/x86_64-pc-linux-gnu/lib/ -isystem /usr/local/x86_64-pc-linux-gnu/include -isystem /usr/local/x86_64-pc-linux-gnu/sys-include -DHAVE_CONFIG_H -I. -I../../../libgo -I ../../../libgo/runtime -I../../../libgo/../libffi/include -I../libffi/include -pthread -L../libatomic/.libs -fexceptions -fnon-call-exceptions -fsplit-stack -Wall -Wextra -Wwrite-strings -Wcast-qual -Werror -minline-all-stringops -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I ../../../libgo/../libgcc -I ../../../libgo/../libbacktrace -I ../../gcc/include -g -O2 -c ../../../libgo/go/golang.org/x/sys/cpu/cpu_gccgo_x86.c -o golang.org/x/sys/cpu_gccgo_x86.o >/dev/null 2>&1 make[4]: *** No rule to make target '../libbacktrace/libbacktrace.la', needed by 'libgo.la'. Stop. make[4]: Leaving directory '/git/gcc/build/x86_64-pc-linux-gnu/libgo' make[3]: *** [Makefile:2347: all-recursive] Error 1 make[3]: Leaving directory '/git/gcc/build/x86_64-pc-linux-gnu/libgo' make[2]: *** [Makefile:1212: all] Error 2 make[2]: Leaving directory '/git/gcc/build/x86_64-pc-linux-gnu/libgo' make[1]: *** [Makefile:22370: all-target-libgo] Error 2 make[1]: Leaving directory '/git/gcc/build' make: *** [Makefile:1082: all] Error 2 When I use instead --enable-languages=all it works (at least worked on the releases/gcc-13 branch on 2023-04-28)
next prev parent reply other threads:[~2023-07-26 18:11 UTC|newest] Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-29 5:49 [Bug bootstrap/106472] New: " sumbera at volny dot cz 2022-07-29 6:29 ` [Bug bootstrap/106472] " pinskia at gcc dot gnu.org 2022-07-29 6:35 ` sumbera at volny dot cz 2022-07-29 8:01 ` rguenth at gcc dot gnu.org 2022-07-29 8:04 ` sumbera at volny dot cz 2022-07-30 8:40 ` roger at nextmovesoftware dot com 2022-07-30 8:53 ` schwab@linux-m68k.org 2022-07-30 9:18 ` roger at nextmovesoftware dot com 2022-07-30 14:02 ` roger at nextmovesoftware dot com 2022-07-30 14:24 ` jakub at gcc dot gnu.org 2022-07-30 14:46 ` schwab@linux-m68k.org 2022-07-30 22:14 ` roger at nextmovesoftware dot com 2022-07-31 7:14 ` cvs-commit at gcc dot gnu.org 2022-08-01 8:55 ` marxin at gcc dot gnu.org 2022-08-10 5:24 ` sumbera at volny dot cz 2022-08-12 10:48 ` jeffrey.rahr at baesystems dot com 2022-08-29 20:49 ` matoro_gcc_bugzilla at matoro dot tk 2022-09-14 12:07 ` tschwinge at gcc dot gnu.org 2022-09-14 14:35 ` jeffrey.rahr at baesystems dot com 2022-09-19 11:37 ` jeffrey.rahr at baesystems dot com 2022-09-19 17:33 ` roger at nextmovesoftware dot com 2022-09-19 18:00 ` jeffrey.rahr at baesystems dot com 2022-11-01 14:05 ` matoro_gcc_bugzilla at matoro dot tk 2022-11-01 14:06 ` matoro_gcc_bugzilla at matoro dot tk 2023-04-26 6:56 ` rguenth at gcc dot gnu.org 2023-05-12 19:49 ` matoro_gcc_bugzilla at matoro dot tk 2023-05-12 19:50 ` matoro_gcc_bugzilla at matoro dot tk 2023-07-26 18:11 ` dilyan.palauzov at aegee dot org [this message] 2023-07-27 9:23 ` rguenth at gcc dot gnu.org 2023-09-10 6:11 ` egallager at gcc dot gnu.org 2023-09-10 6:34 ` egallager at gcc dot gnu.org 2023-09-10 13:42 ` matoro_gcc_bugzilla at matoro dot tk 2023-09-11 4:27 ` egallager at gcc dot gnu.org 2023-10-24 20:33 ` daniel.melendrezarmada at manchester dot ac.uk 2024-03-10 19:34 ` dilyan.palauzov at aegee dot org 2024-03-13 0:05 ` egallager at gcc dot gnu.org 2024-03-13 6:21 ` dilyan.palauzov at aegee dot org 2024-03-29 15:02 ` jakub at gcc dot gnu.org 2024-04-02 11:41 ` cvs-commit at gcc dot gnu.org 2024-04-21 4:08 ` cvs-commit at gcc dot gnu.org 2024-04-21 13:02 ` dilyan.palauzov at aegee dot org 2024-04-23 6:46 ` jakub at gcc dot gnu.org 2024-04-23 6:47 ` jakub 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-106472-4-j1GiHv7IlX@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).