From: Simon Marchi <simark@simark.ca>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>,
gdb-patches@sourceware.org
Cc: indu.bhagat@oracle.com, elena.zannoni@oracle.com
Subject: Re: [Mike Frysinger] Re: [PATCH, V3 10/15] gdb: sim: buildsystem changes to accommodate libsframe
Date: Fri, 4 Nov 2022 10:46:40 -0400 [thread overview]
Message-ID: <c2d71cbe-8ccf-2760-3e76-0bfc14f0e466@simark.ca> (raw)
In-Reply-To: <87y1srrkpy.fsf@oracle.com>
> But first things first: how do you people feel about libtoolizing the
> rules in gdb/Makefile.in so GDB can handle the in-tree libtool libraries
> in a more graceful way?
What does "libtoolizing the rules" mean, in practice?
Simon
next prev parent reply other threads:[~2022-11-04 14:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 12:02 Jose E. Marchesi
2022-11-04 13:59 ` Elena Zannoni
2022-11-04 14:46 ` Simon Marchi [this message]
2022-11-04 15:20 ` Jose E. Marchesi
2022-11-04 15:36 ` Jose E. Marchesi
2022-11-04 16:04 ` Simon Marchi
2022-11-05 8:25 ` Mike Frysinger
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=c2d71cbe-8ccf-2760-3e76-0bfc14f0e466@simark.ca \
--to=simark@simark.ca \
--cc=elena.zannoni@oracle.com \
--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).