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: pedwards at disaster dot jaj dot com (Phil Edwards)
- Subject: Re: forget *documenting* libiberty -- how about *installing* it?
- From: Joe Buck <jbuck at racerx dot synopsys dot com>
- Date: Wed, 3 Jan 2001 17:26:20 -0800 (PST)
- Cc: gcc at gcc dot gnu dot org
> Can we consider adding installation rules for the libiberty header files?
> The only suggestion I have for "where" is the obvious one of "in a libiberty
> subdir" so that users would need to write
>
> #include <libiberty/splay-tree.h>
> #include <libiberty/md5.h>
>
> and so forth.
In the past, when things like this were discussed the issue always came up
that, currently, binutils and gdb both ship a libiberty and they are
usually out of phase with each other. So libiberty doesn't really have
a version number and it's a problem if you use an installed copy because
depending on the order in which gdb, binutils and gcc are installed you
might get a different one. Any news on that front? Or is it still the
same?