public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/29372] slibtool build failure - make[2]: *** No rule to make target '../bfd/libbfd.a', needed by 'gdb'. Stop.
Date: Mon, 18 Jul 2022 19:03:51 +0000 [thread overview]
Message-ID: <bug-29372-4717-q2DsI0pQrb@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29372-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29372
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
I don't know anything about slibtool, but it sounds like
maybe the provided build system is being modified to work
with it?
gdb doesn't use libtool for linking but does seem to use
the workaround:
BFD_DIR = ../bfd
BFD = $(BFD_DIR)/libbfd.a
Changing gdb to use libtool for linking seems fine to me,
as long as it doesn't slow down the whole build somehow.
You may have to find all the subdirectories relying on this hack.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-07-18 19:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 21:07 [Bug build/29372] New: " orbea at riseup dot net
2022-07-18 19:03 ` tromey at sourceware dot org [this message]
2022-07-20 2:38 ` [Bug build/29372] " orbea at riseup dot net
2022-07-20 2:45 ` orbea at riseup dot net
2022-11-05 5:51 ` sam at gentoo dot org
2022-11-05 8:26 ` vapier at gentoo dot org
2022-11-06 2:51 ` [Bug build/29372] build failure when using slibtool to replace libtool " vapier at gentoo dot org
2022-11-08 21:59 ` tromey at sourceware dot org
2022-11-08 22:45 ` orbea at riseup dot net
2022-11-09 2:21 ` tromey at sourceware dot 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-29372-4717-q2DsI0pQrb@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.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).