Re: `--prefix /foo' mishandled in sub-configure invocation

[Raja R Harinath]

Alexandre Duret-Lutz <address@hidden> writes:

>>>> "Ralf" == Ralf Corsepius <address@hidden> writes:
> [...]
>  Ralf> Well, supporting "--prefix foo" is a _bug_, IMO, because it is an
>  Ralf> exception from the rules (Why isn't --includedir foo supported?).
[snip]
>   1) `--includedir foo' is supported, as are all other options

Yep.  Even though it is not listed in the case statement in
lib/autoconf/status.m4, it gets through all right because of the
catchall '*' clause.  (I guess this was the reason for Ralf's confusion.)

The reason for the special treatment of 'prefix' is mentioned in the
comment below the case:

  # Always prepend --prefix to ensure using the same prefix
  # in subdir configurations.

So, if I invoke the toplevel configure with

  ../../configure --disable-static --enable-maintainer-mode \
    --includedir ~/foo --prefix ~/bar -C

the subdir configure gets invoked as

  ../../../subdir/configure --prefix=/home/mine/bar --disable-static \
    --enable-maintainer-mode --includedir /home/mine/foo \
    --cache-file=../config.cache --srcdir=../../../subdir

- Hari
-- 
Raja R Harinath ------------------------------ address@hidden
"When all else fails, read the instructions."      -- Cahn's Axiom
"Our policy is, when in doubt, do the right thing."   -- Roy L Ash