This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: forget *documenting* libiberty -- how about *installing* it?
- To: Phil Edwards <pedwards at disaster dot jaj dot com>
- Subject: Re: forget *documenting* libiberty -- how about *installing* it?
- From: Jeffrey A Law <law at redhat dot com>
- Date: Wed, 03 Jan 2001 21:07:19 -0700
- cc: gcc at gcc dot gnu dot org
- Reply-To: law at redhat dot com
In message <20010102180811.A1612@disaster.jaj.com>you write:
>
> The README file for libiberty starts off:
>
> This directory contains the -liberty library of free software.
> It is a collection of subroutines used by various GNU programs.
> ...
> We expect many of the GNU subroutines that are floating around to
> eventually arrive here.
>
> I was writing the chunk of libiberty.texi on "how to use these subroutines
> in various GNU programs that you the friendly user might be writing" when
> I remembered that we never install header files for libiberty; only the
> actual .a file.
That can be fixed easy enough :-)
> Can we consider adding installation rules for the libiberty header files?
Yes.
> The only suggestion I have for "where" is the obvious one of
> "in a libiberty subdir" so that users would need to write
Either $(prefix)/include or $(prefix)/include/libiberty would make the
most sense to me.
jeff