From: Sergei Trofimovich <slyich@gmail.com>
To: gcc-patches@gcc.gnu.org
Cc: Thomas Schwinge <thomas@codesourcery.com>,
Ian Lance Taylor <ian@airs.com>,
Sergei Trofimovich <siarheit@google.com>
Subject: [PATCH] Add libgo dependency on libbacktrace.
Date: Thu, 18 Aug 2022 07:59:50 +0100 [thread overview]
Message-ID: <20220818065950.440702-1-slyich@gmail.com> (raw)
From: Sergei Trofimovich <siarheit@google.com>
Noticed missing dependency when regenerated Makefile.in for unrelated
change with 'autoget Makefile.def'.
The change was lost in basepoints/gcc-12-6861-gaeac414923a
("Revert "Fix PR 67102: Add libstdc++ dependancy to libffi" [PR67102]").
/
Makefile.in: Regenerate.
---
Makefile.in | 1 +
1 file changed, 1 insertion(+)
diff --git a/Makefile.in b/Makefile.in
index 13ee95a2602..60077a6aa36 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -66523,6 +66523,7 @@ all-target-liboffloadmic: maybe-all-target-libgomp
configure-target-newlib: maybe-all-binutils
configure-target-newlib: maybe-all-ld
configure-target-libgfortran: maybe-all-target-libbacktrace
+configure-target-libgo: maybe-all-target-libbacktrace
@endunless gcc-bootstrap
# Dependencies for target modules on other target modules are
--
2.37.1
next prev reply other threads:[~2022-08-18 6:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-30 21:38 [PATCH] PR bootstrap/106472: Add libgo depends on libbacktrace to Makefile.def Roger Sayle
2022-07-31 1:21 ` Ian Lance Taylor
2022-08-18 6:59 ` Sergei Trofimovich [this message]
2022-09-14 12:06 ` [PATCH] Add libgo dependency on libbacktrace Thomas Schwinge
2022-09-27 1:49 ` Jeff Law
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=20220818065950.440702-1-slyich@gmail.com \
--to=slyich@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ian@airs.com \
--cc=siarheit@google.com \
--cc=thomas@codesourcery.com \
/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).