From: Mike Frysinger <vapier@gentoo.org>
To: Simon Marchi <simark@simark.ca>
Cc: "Jose E. Marchesi" <jose.marchesi@oracle.com>,
gdb-patches@sourceware.org, indu.bhagat@oracle.com,
elena.zannoni@oracle.com
Subject: Re: [PATCH V2] gdb: link executables with libtool
Date: Sun, 6 Nov 2022 09:51:04 +0700 [thread overview]
Message-ID: <Y2chGOZjMtldE0UG@vapier> (raw)
In-Reply-To: <242f99e5-2c41-155a-3bd9-e0c96dea28f5@simark.ca>
[-- Attachment #1: Type: text/plain, Size: 826 bytes --]
On 05 Nov 2022 12:38, Simon Marchi via Gdb-patches wrote:
> On 11/5/22 10:02, Jose E. Marchesi via Gdb-patches wrote:
> > LIBBACKTRACE_LIB now refers to ../libbacktrace/libbacktrace.la
> > LIBCTF now refers to ../libctf/libctf.la
>
> The patch linked in this bug:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=29372
>
> also updated OPCODES to use $(OPCODES_DIR)/libopcodes.la, should you do
> it too?
yeah, and i think we can drop zlib & zstd logic too since they're in there
only for bfd. less sure about gettext usage ... if gdb uses gettext, we
want to keep it, but if it was pulled in only for bfd too, we can purge it
from the gdb side.
although i'm totally fine with doing the zlib & zstd cleanup as a followup
commit since Jose's patch here improves the status quo.
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-11-06 2:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 14:02 Jose E. Marchesi
2022-11-05 16:38 ` Simon Marchi
2022-11-06 2:51 ` Mike Frysinger [this message]
2022-11-06 11:45 ` Jose E. Marchesi
2022-11-06 13:04 ` Jose E. Marchesi
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=Y2chGOZjMtldE0UG@vapier \
--to=vapier@gentoo.org \
--cc=elena.zannoni@oracle.com \
--cc=gdb-patches@sourceware.org \
--cc=indu.bhagat@oracle.com \
--cc=jose.marchesi@oracle.com \
--cc=simark@simark.ca \
/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).