Re: Bug#372179: AC_CANONICAL_SYSTEM overwrites $@

[Justin Erenkrantz]

On 6/19/06, Tollef Fog Heen <address@hidden> wrote:
> * Ralf Wildenhues
>
> | Hello Justin, Tollef,
> |
> | * Justin Erenkrantz wrote on Sun, Jun 18, 2006 at 11:40:12PM CEST:
> | > On 6/18/06, Tollef Fog Heen <address@hidden> wrote:
> | > >Currently, if configure is passed --sbindir=, it just overrides
> | > >$sbindir without flagging that at all.  If it, in addition to changing
> | > >$sbindir, it'd set ac_param_sbindir either to 1 to show that sbindir
> | > >is derviced from a command line argument or to the value passed on the
> | > >command line.  If we had this, APR_LAYOUT could check if
> | > >ac_param_sbindir was set, and if so skip setting sbindir from the
> | > >layout.
> | > >
> | > >Would this be an acceptable solution for both the APR and the autoconf
> | > >people?
> | >
> | > That could work for our purposes, yes.  It'd be cleaner to boot, too.
> |
> | So what do you do with
> |   --bindir=/foo --with-layout=bar --sbindir=/baz
> |
> | shouldn't the bar layout override bindir but not sbindir?  (Note I don't
> | know the exact semantics --with-layout is supposed to have.)
>
> IMO, command line ordering shouldn't matter, unless you do
> --bindir=/foo --bindir=/bar.  --with-layout just changes the defaults,
> it doesn't override the state you're currently in.

Correct.  Anything explicitly provided on the command-line is
literally respected - the layout file just allows the user to change
autoconf's defaults in a straightforward manner.  -- justin