This is the mail archive of the binutils@sourceware.cygnus.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]

Re: A patch for cross compiling checking


"H . J . Lu" wrote:
> 
> On Sat, May 20, 2000 at 11:14:53AM +1000, Andrew Cagney wrote:
> > "H . J . Lu" wrote:
> > >
> > > On Sat, May 20, 2000 at 10:49:08AM +1000, Andrew Cagney wrote:
> > > >
> > > > Does this test require that a GCC cross compiler be built/installed
> > > > before the configure goes ahead?
> > >
> > > No. You just need to do
> > >
> > > # mkdir -p ${prefix}/lib/gcc-lib/${target_alias}/${gcc_version}
> > >
> > > or add --disable-target-dir-sanity-checking to configure.
> >
> > But why should I have to do that now?
> >
> 
> It is not a problem with newlib. But it is a problem for non-newlib.
> gcc uses ${prefix}/lib/gcc-lib/${target_alias}/${gcc_version}/../../xxxxx
> to find the C header files if the C library is not newlib. With this
> patch, people who build Linux/ia64 toolchain on ia32 will know what
> goes wrong.

Sorry, you've really lost me, where does newlib come in?  Hmm.... I
suspect it is to do with building a full cross compliation environment
for GNU/Linux/ia64 - rather than just GCC et.al.

Assuming that is the problem, could you please expand on the procedure
that people are being told to follow when performing this task (and
where they divert from that procedure).

	Andrew

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