public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>,
	Eli Zaretskii <eliz@gnu.org>
Cc: indu.bhagat@oracle.com, gdb-patches@sourceware.org,
	elena.zannoni@oracle.com
Subject: Re: [PATCH] gdb: link executables with libtool
Date: Sat, 5 Nov 2022 12:40:16 -0400	[thread overview]
Message-ID: <5a5ce25a-5baf-2bb1-d016-97ccf617ba25@simark.ca> (raw)
In-Reply-To: <871qqhiicr.fsf@oracle.com>



On 11/5/22 10:30, Jose E. Marchesi via Gdb-patches wrote:
> 
>>> Date: Sat,  5 Nov 2022 14:08:27 +0100
>>> From: "Jose E. Marchesi via Gdb-patches" <gdb-patches@sourceware.org>
>>> Cc: indu.bhagat@oracle.com, elena.zannoni@oracle.com
>>>
>>> This patch changes the GDB build system in order to use libtool to
>>> link the several built executables.  This makes it possible to refer
>>> to libtool libraries (.la files) in CLIBS.
>>
>> If this is supposed to be installed before we start the release cycle
>> of GDB 13, I question the wisdom of making such a significant change
>> when we are so close to the next release.
>>
>> Does this solve some grave problems, or can we wait until after GDB
>> 13?
> 
> Basically it would unstuck us in getting the SFrame integration applied
> in binutils.
> 
> See
> https://sourceware.org/pipermail/gdb-patches/2022-November/193381.html
> 
> We could go with the simpler solution suggested in that email (already
> used by libbacktrace and libctf) in GDB 13 and then we can apply the new
> patch to switch to libtool for linking.
> 
> I know Mike doesn't like the idea; but I hope we have proved we do our
> homework?

IIUC, it would not be useful to have the libtool changes without the
SFrame changes.  And given that the GDB 13 branch is supposed to be cut
very shortly, do we expect to have the SFrame changes in GDB 13 (I have
no idea what that consists of)?  If not, then the libtool changes are
not really needed in GDB 13.

Simon

  reply	other threads:[~2022-11-05 16:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-05 13:08 Jose E. Marchesi
2022-11-05 13:26 ` Eli Zaretskii
2022-11-05 14:30   ` Jose E. Marchesi
2022-11-05 16:40     ` Simon Marchi [this message]
2022-11-05 18:04       ` Jose E. Marchesi
2022-11-06  0:57         ` Simon Marchi
2022-11-06  2:46         ` Mike Frysinger
2022-11-06  5:57           ` Indu Bhagat
2022-11-06  6:22           ` Eli Zaretskii

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=5a5ce25a-5baf-2bb1-d016-97ccf617ba25@simark.ca \
    --to=simark@simark.ca \
    --cc=elena.zannoni@oracle.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=indu.bhagat@oracle.com \
    --cc=jose.marchesi@oracle.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).