Re: Why doesn't config.log quote invocation command line?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Bob,

* Bob Friesenhahn wrote on Sun, Oct 10, 2010 at 04:22:41PM CEST:
> On Fri, 8 Oct 2010, Ralf Wildenhues wrote:
> >
> >For that please use
> > ./config.status --config
> >
> >It is properly quoted for eval.  It is new in 2.65.
> 
> I have always used './config.status --version'.  There was a time
> when the output of --version could be completely reused as is but
> then someone decided it should be more pretty so now it requires two
> cut-and-paste operations.

Yes, because of GNU Coding Standards requirements on --version output.

> This is something I use quite often in
> order to create similar builds with somewhat different options.  I
> see that the output of --config is incomplete because it does not
> reveal the location of the configure script used to generate it.

That, too, is on purpose, so you can easily reuse the switches for a
different package, or from a different build directory.

You can still get the source directory path with
  echo @srcdir@ | ./config.status --file=-

if you don't want to extract it from --version output (which is a good
thing, I guess).

Cheers,
Ralf

_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf


[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux