From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA 2/3] Import vsnprintf from libiberty if not available.
Date: Wed, 23 Jun 2010 19:19:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1006231909300.22427@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1277315177-17869-3-git-send-email-brobecker@adacore.com>
On Wed, 23 Jun 2010, Joel Brobecker wrote:
> The long-term goal in this area is to start using gnulib instead of
> libiberty, so I will look at that in the short future. But in the
As a general principle, gnulib and libiberty serve similar purposes and I
don't believe the GNU Project needs two different libraries in this area
(furthermore, both gnulib and libiberty import many files from glibc,
though libiberty often has accumulated many local changes to these files).
In practice I expect it would be a lot of work to convert libiberty-using
software to gnulib, or to make libiberty import most of its files
unchanged from gnulib and so be more of a wrapper around gnulib, and the
benefits would be limited - but certainly it seems a good idea for more
self-contained software such as gdbserver.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2010-06-23 19:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 17:46 Add support for ppc-lynxos to GDBserver Joel Brobecker
2010-06-23 17:46 ` [RFA 3/3] gdbserver support for powerpc-lynxos (4.x) Joel Brobecker
2010-07-27 16:13 ` Pedro Alves
2010-08-31 19:38 ` Joel Brobecker
2010-08-31 20:24 ` Pedro Alves
2010-09-01 18:36 ` Joel Brobecker
2010-09-01 18:42 ` Pedro Alves
2010-09-01 19:00 ` Joel Brobecker
2010-06-23 17:46 ` [RFA 2/3] Import vsnprintf from libiberty if not available Joel Brobecker
2010-06-23 19:19 ` Joseph S. Myers [this message]
2010-06-24 12:08 ` Pierre Muller
2010-06-24 12:40 ` Pierre Muller
2010-06-23 17:46 ` [RFA 1/3] Generate regformats/rs6000/powerpc-32.dat Joel Brobecker
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=Pine.LNX.4.64.1006231909300.22427@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@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).