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: Installed location of 'as' for cross targets (--enable-targets)


On Tue, Sep 16, 2003 at 01:23:33PM -0700, H. J. Lu wrote:
> On Tue, Sep 16, 2003 at 03:51:40PM -0400, Carlos O'Donell wrote:
> > > The behaviour of the configure script is in flux, and may be
> > > permanently changing.  When you specify --host, the gas configure
> > > script now thinks you are building a cross-assembler, even when --host
> > > and --build are the same.
> > 
> > Knowing it's in flux is half the battle.
> >  
> > > The fix may be to only specify --build.  But then that may not work at
> > > the top level.  Not sure.
> > 
> 
> You can try this
> http://sources.redhat.com/ml/binutils/2003-09/msg00046.html
> H.J.

Before patch:
- 'as' is only copied to $PREFIX/$TARGET/bin

After patch:
- 'as' is copied to $PREFIX/bin as '$TARGET-as'

Getting better, I still need to symlink that as '$TARGET64-as'
(hppa64-linux-as) for the rest of the toolchain to understand it's
"multi-arch" nature. Shouldn't we generate a symlink for all the targets
in "--enable-targets" and place them in $PREFIX/bin and symlink them
against original binary in $PREFIX/bin?

I should probably search the list to look for any historical reasons.

c.


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