reworking cross configs (was Re: Patch for libstdc++-v3 cross build on hpux (Resubmit^2))

[Phil Edwards]

On Sat, Jun 08, 2002 at 07:15:48AM -0700, Benjamin Kosnik wrote:
> > Steve, let me clean this file up, sanity-check my changes with other
> > people, and then I'll apply an updated version of your patch.  (And
> > notify you of the changed version.)  The cross-compile section of
> > configure.in has quadrupled in size (not a bad thing in itself, it
> > means more people are using it) since the last time I paid attention
> > to it, and I'm getting confused.
> 
> Thanks for looking at this PHil.
> 
> That host-x-host part intially went in as a complete hack. Perhaps it's
> time to re-think it entirely, since it seems to be used by many people
> now. If there's a better way to organize this code, then feel free to do
> major surgery.

Well, apart from my other questions on CHECK_*_FEATURES, I haven't been
able to touch much of configure.in yet.  More comments, basically.

I was able to clean up configure.target a fair amount.

It occurred to me that configure.host was pointless, so I plan to delete it.
(I was the one who originally broke configure.target and .host out into
separate files, but at the time I didn't fully appreciate the naming
conventions that rename "target" at the top level into "host" at the
library level.)

That patch will be posted later today; I want to see if anyone has comments
on the CHECK_*_FEATURES questions.


One of the problems preventing cleanup is that autoconf has no #include
facility, so we can't break the handcrafted cross-compile sections out
into their own file(s) without completely changing their format.  This will
take some more thought.


Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams