Re: bfd.h installation location

["H . J . Lu" <hjl at lucon dot org>]

On Wed, May 15, 2002 at 04:22:57PM +0930, Alan Modra wrote:
> On Mon, May 13, 2002 at 05:44:03AM -0300, Alexandre Oliva wrote:
> > On May 13, 2002, "H . J . Lu" <hjl@lucon.org> wrote:
> > 
> > > On Mon, May 13, 2002 at 03:46:02AM -0300, Alexandre Oliva wrote:
> > >> > Yes, you're right.  Hmm, all this fussing over headers applies equally
> > >> > to libbfd.a.
> > >> 
> > >> Hmm...  Indeed.
> > >> 
> > >> But then, as H.J.Lu says, $(toolexecdir), which I have proposed, is
> > >> not correct, as it contains libraries in the target format, not
> > >> libraries for the host with information about the target.
> > 
> > > It is hardly a new problem.
> > 
> > Nobody said it was new.  It is just wrong.  Even if
> > --enable-targets=all is in use, you still have a different default in
> > place.
> 
> OK, getting back to this problem.  The only reasonable solutions I see
> are to a) only install libbfd.a and headers when host == target, or
> b) install normally when host == target, and install as
> $target_alias-libbfd.a and $target_alias-bfd.h etc. otherwise.
> Case b) is similar to the way we install tools like objdump.
> 
> Otherwise you need to supply different prefixes or you'll overwrite
> libbfd.a and headers when compiling for different targets.

You will overwrite libbfd.a and headers for different targets only
when host != target. I don't know any problems when host == target.

Under /export/tools, the host machine, Linux/x86, shares the same
set of libbfd and bfd.h with 3 different targets, i386-linux, 
mipsel-linux and mips-linux. But each target has its own libbfd
and bfd.h under /export/tools/i386-linux /export/tools/mipsel-linux
and /export/tools/mips-linux, respectively.

Please don't introduce any new problems.


H.J.