public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sumbera at volny dot cz" <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: Fri, 29 Jul 2022 06:35:08 +0000 [thread overview]
Message-ID: <bug-106472-4-CibZpHknuz@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
--- Comment #2 from Petr Sumbera <sumbera at volny dot cz> ---
(In reply to Andrew Pinski from comment #1)
> Are you building in the source tree?
No. I'm building it outside of source tree. GCC 11 and older don't seem to have
this problem.
next prev parent reply other threads:[~2022-07-29 6:35 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 [this message]
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
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-CibZpHknuz@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).