Re: HEAD: workaround for released autotools

[Gary V. Vaughan]

Hallo Ralf,

On 29 Aug 2005, at 12:53, Ralf Wildenhues wrote:
> Nono, that's still not what I mean.  The line in m4general.m4sh is  
> fine.
> You call plain
>   ./configure
> but I have setups where that does not work.
>
> To be pedantic: the GNU build system is just not designed to build
> out-of-the-box everywhere.  The goal is to provide a consistent user
> interface.  So, if I want to build 100 packages, all I may have to do
> on machine X is
>   ./configure CFLAGS=-foo && make && su -c "make install"
> and on machine Y it is
>   ./configure CFLAGS=-bar && make && su -c "make install"
>
> But you can't expect plain "configure" without options to work.
> And I test on real-world systems where this is true.

ACK.  We run plain configure in our test/*demo tests, and some of our  
new
autotest btw...


> > If you really hate this patch, then we can apply yours instead.  I'd
> > still like some method of being able to make the 2.0 release without
> > the  duplicate files if we have the necessary autotool patches in
> > place at bootstrap  time though.  Maybe an environment variable?
>
> That would be fine with me.  Or a commandline switch for `bootstrap',
> FWIW.

K.  Can you add that (either/or) and commit your original patch please?

Cheers,
    Gary.
--
Gary V. Vaughan      ())_.  gary@ 
{lilith.warpmail.net,gnu.org},address@hidden
Research Scientist   ( '/   http://www.tkd.kicks-ass.net
GNU Hacker           / )=   http://www.gnu.org/software/{libtool,m4}
Technical Author   `(_~)_   http://sources.redhat.com/autobook

PGP.sig
Description: This is a digitally signed message part