Re: cross-builds failing

[Richard Earnshaw <rearnsha at arm dot com>]

> 
>   In message <199810060909.KAA06594@sun52.NIS.cambridge>you write:
>   > 
>   > I'm not sure why this has started (or exactly when -- sometime in the last 
>   > couple of weeks I think).  I have a cross-build for the ARM set up, with a 
>   > gas and newlib tree linked into my source structure.  In the past this has 
>   > always built fine (modulo a few small problems with the latest gas 
>   > snapshots putting intl in a different place).
> Probably the libunsubdir problem.
> 
> Wait, presumably you did specify --with-headers= right?

Wrong.  I've got newlib as part of my source tree.  Why should that be 
needed?  Surely it should pick up newlib in the same way gas gets found if 
that is part of the source tree (for which I don't need to say 
--with-as=... or whatever).

Anyway, the configure.in script has a comment in which says, 

 # If both --with-headers and --with-libs are specified, default to
 # --without-newlib.

which is not what I want, since I want newlib.

If some special magic is required, can't configure.in fake it up if it 
decides it is building a newlib in the source tree.

>   > Thinking back, didn't gcc always used to look in <prefix>/<target>/include   > ?
> Yes, we are still supposed to look at <prefix>/<target_alias>/include.
> 

Well it doesn't seem to be...

Richard.