Binutils - Chapter Six: libiberty header files, and Trac #1929

[Trent Shea]

Hi,


I'm looking at binutils in chapter six, and how we are copying libiberty.h to 
its final location. For the record, I've been working with binutils-2.19.1.

The configure option --enable-install-libiberty should "Install headers for 
end users," unfortunately, I can't get it to work (well, see below.) 

GCC also ships with libiberty and --enable-install-libiberty works as I'd 
expect (IE. header files get installed.) Previous discussion on this mailing 
list indicates that binutils has historically distributed a newer version, and 
that its version is the preferred choice. I list GCC as an example to show 
that there are other packages that distribute libiberty, and that they are 
configurable in such a way that the headers get installed. Perhaps it may be 
appropriate to report upstream that --enable-install-libiberty has no effect?

After looking at libiberty I wonder which header files should be installed. 

The list of header files can be generated the following ways.
With gcc:
configure with --enable-install-libiberty
With binutils:
configure --with-target-subdir=anything --enable-install-libiberty

The header files are as follows (installed in /usr/include/libiberty):
ansidecl.h (gets duplicated)
demangle.h 
dyn-string.h
fibheap.h
floatformat.h
hashtab.h
libiberty.h
objalloc.h
partition.h
safe-ctype.h
sort.h
splay-tree.h

My opinion is that all of the header files should be installed, as if the 
configure option worked. Unfortunately, I don't see an elegant way around the 
cp command.

I'm still in the early stages of researching this, but I'd appreciate any 
input; mainly, whether or not installing all of the archive's header files 
should be considered.


Regards,
Trent.