Re: [autoconf-conversion] Re: Toplevel configury, multilibs, new autoconf versions

[Phil Edwards <phil at jaj dot com>]

On Sun, Jul 27, 2003 at 04:49:26PM -0700, Zack Weinberg wrote:
> Phil Edwards <phil@jaj.com> writes:
> 
> > So, when the primary v3 configure is run,
> > the toplevel does it via
> >
> >     CXX=Primary $srcdir/configure --stuff
> >
> > Clear?
> >
> > Now, at the end of that run, config.status is generated and executed.
> > It source's config-ml.in, which runs through the list of multilib subdirs,
> > and does text substitution on the env variables.  Pretend we have one
> > multilib, and I'll call the CXX variable for that one Multilib:
> >
> >     # config-ml.in does this
> >     Multilib=`echo Primary | sed 's/references-to-primary-dir/references-to-multilib-dir'`
> >
> >     cd up-and-over-to-multilib-dir/libstdc++-v3
> >     CXX=Multilib $srcdir/configure --stuff
> 
> It seems to me that the problem is right here: we shouldn't have this
> Primary/Multilib distinction in the first place.  Suppose we hoist all
> the iteration over multilibs up to the top level Makefile.  Then each
> multilib directory gets configured as a 'primary' and the symptoms
> you've observed vanish.
> 
> I want this for other reasons - specifically, I want to be able to set
> up a multilib set that doesn't have any primary (default).

Nathanael also wants this, and I think it would probably be a good idea.

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