This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: bfd.h installation location


On Mon, May 13, 2002 at 03:32:02PM +0930, Alan Modra wrote:
> On Mon, May 13, 2002 at 02:18:26AM -0300, Alexandre Oliva wrote:
> > On May 12, 2002, Alan Modra <amodra@bigpond.net.au> wrote:
> > > bfd/ChangeLog
> > > 	* Makefile.am (install-data-local): Install headers to
> > > 	$(exec_prefix)/include.
> > > 	* Makefile.in: Regenerate.
> > 
> > I'm afraid this is not enough.  exec_prefix/include may still be
> > shared by compilers for different targets.  We should install bfd.h in
> > $(toolexecdir)/include or so.
> 
> Yes, you're right.  Hmm, all this fussing over headers applies equally
> to libbfd.a.  I think I need to copy some of the trickery in
> libiberty/Makefile.in.  ie. install headers and libbfd to $libdir when
> native, and to tooldir ($(exec_prefix)/$(target_alias)) for cross
> targets.

Are you sure this is ok? As far as I know, $(exec_prefix)/$(target_alias)
is for the cross target, not the host machine. That is on x86 host,
/export/tools/mipsel-linux/lib and /export/tools/mipsel-linux/include
are for mipsel-linux.


H.J.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]