public inbox for
 help / color / mirror / Atom feed
From: "Mark D. Baushke" <>
To: "Mike M. Volokhov" <>
Subject: Re: Removing libiberty (was Re: gnatsd problems with 4.0.1)
Date: Wed, 09 Feb 2005 17:15:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Mike M. Volokhov <> writes:

> On Mon, 07 Feb 2005 09:09:20 -0800
> "Mark D. Baushke" <> wrote:
> > Mike M. Volokhov <> writes:
> [snip]
> > > So, only six functions are used by GNATS, when libiberty provides about
> > > 40. Only two functions (asprintf and vasprintf) are nor POSIX nor
> > > standard C relevant (but included in both GNU and BSD libc). Three
> > > functions (xstrdup, xmalloc, xrealloc) are totally libiberty-own, but
> > > can be easy replaced with their standard equivalents.
> > > 
> > > Thus, I propose to eliminate dependency on libiberty completely.
> > > 
> > > Any comments?
> > 
> > I would suggest consideration of including the GNULIB versions of those
> > functions as an alternative.
> Some libiberty functions, such as getopt, was moved to GNU, BSD and
> other C libraries. Many (like some x* ones) are very simple. Please try
> a patch (see my another message within "Removing libiberty" topic) which
> utilizes many functions from standard libc, shipped with build OS.
> Another reason to use libc native to OS, is optimization.

The reason to use GNULIB is consistent functional results. Some of the
GNULIB functions implement full POSIX semantics while the OS version may

> Anyway, as for me, GNULIB is better way than have libiberty in tree.
> Thanks for pointing it out!

You are welcome.

> [snip]
> > The typical approach would be to create a lib and m4 directory for
> > including the relevant code from a gnulib checkout directory into the
> > gnats source base. There is a tool that can be used to pull into the
> > gnats tree any module that GNULIB provides.
> Does GNULIB provides the shared library (.so)? If so, there is would no
> need to create extra directories in GNATS tree.

No, the GNULIB provides a set of replacement or wrapper functions along
with automake and autoconf glue to put them all together. However, each
separate project that uses the GNULIB will only be using a subset of the
functions and .h files that are available for GNULIB as a whole, so there
is no single .so that has everything in it.

While I suppose that you could create some kind of a that
includes those functions which gnats needs, it would be up to you to
specify things properly in the to do that generation,
possibly in conjuction with libtool

	-- Mark

Help-gnats mailing list

  reply	other threads:[~2005-02-09 17:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-05 18:23 gnatsd problems with 4.0.1 Tim Buck
2005-01-05 22:24 ` Chad Walstrom
2005-01-06  9:18   ` Mike M. Volokhov
2005-01-06 17:07     ` Chad Walstrom
2005-02-07 15:47       ` Mike M. Volokhov
2005-02-07 17:15         ` Mark D. Baushke
2005-02-07 19:17           ` Chad Walstrom
2005-02-09 12:50           ` Removing libiberty (was Re: gnatsd problems with 4.0.1) Mike M. Volokhov
2005-02-09 17:15             ` Mark D. Baushke [this message]
2005-02-07 17:45         ` Chad Walstrom
2005-02-09 10:56           ` Mike M. Volokhov
     [not found]             ` <>
     [not found]               ` <>
2005-02-24 22:17                 ` Soon to come: RC3 Chad Walstrom
2005-02-24 22:40                   ` RC2 (was Re: Soon to come: RC3) Chad Walstrom
2005-01-06 16:03   ` gnatsd problems with 4.0.1 Tim Buck

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).