i like to record the flags used when running `./configure` to be shown when
running --version info with programs. yes, i'm aware of option quoting issues
and env vars not being saved and all those other fun details, but those are
irrelevant to me. vast majority of the time, the configure flags
* Mike Frysinger wrote on Tue, Mar 10, 2009 at 08:01:49AM CET:
> i like to record the flags used when running `./configure` to be shown when
> running --version info with programs.
Undocumented (so watch out when updating Autoconf), but:
eval "$ac_configure_args"
should provide you with what y
On Tuesday 10 March 2009 03:18:26 Ralf Wildenhues wrote:
> * Mike Frysinger wrote on Tue, Mar 10, 2009 at 08:01:49AM CET:
> > i like to record the flags used when running `./configure` to be shown
> > when running --version info with programs.
>
> Undocumented (so watch out when updating Autoconf),
On Tuesday 10 March 2009 07:18:26 Ralf Wildenhues wrote:
> Undocumented (so watch out when updating Autoconf), but:
> eval "$ac_configure_args"
Didn't that get clobbered, in some not so distant past releases?
(autoconf-2.60 and 2.61 IIRC; I can't remember if it was fixed in
2.62 or not, but i
On Tuesday 10 March 2009 06:49:12 Keith Marshall wrote:
> On Tuesday 10 March 2009 07:18:26 Ralf Wildenhues wrote:
> > I suppose Autoconf could provide a macro to access this variable
> > which we could then document.
>
> That would be useful. I've used $ac_configure_args, filtered, to pass
> to a
Hello Keith,
* Keith Marshall wrote on Tue, Mar 10, 2009 at 11:49:12AM CET:
> On Tuesday 10 March 2009 07:18:26 Ralf Wildenhues wrote:
> > Undocumented (so watch out when updating Autoconf), but:
> > eval "$ac_configure_args"
>
> Didn't that get clobbered, in some not so distant past releases?
