This is the mail archive of the
mailing list for the GCC project.
Re: [autoconf-conversion] Re: Toplevel configury, multilibs, new autoconf versions
On Sun, Jul 27, 2003 at 07:33:13PM -0400, Phil Edwards wrote:
> When configure examines the command line and sees variable assignments,
> it performs them without examining the current environment. It does this
> for safety, because it thinks the user is rerunning configure.
> That sound you hear is configure wailing, "MY PRECIOUSSSSSSSS!" as it
> overwrites Multilib with Primary.
> I've made a couple of half-hearted attempts to defeat this from within
> libstdc++'s acinclude.m4, but autoconf is too smart for me.
I wasn't being evil enough.
*cackle* I have sneakily removed the bit of shell code in configure which
treats CXX as a "precious" variable. Other precious variables are still
passed around but CXX is correctly inherited from the environment like we
want it to be.
(Since libstdc++ is no longer shipped on its own, I'm not worried about
end-users making the reconfigure mistake. The library is /always/
configured via the toplevel.)
This works, and unless somebody has better suggestions, I'm probably going
to use it for a short-term fix. How short? Long enough to complete the
transition to the new tools and check things in, where other people can
begin hacking on them.
Moving multilib knowledge to the toplevel is sounding better and better
as the proper solution, at which point the evil can be removed.
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