Hmm.. unset is used at numerous places in our configure.in file, so it
should be portable within our audience...
Can we have automake on squid-cache.org patched to use unset for now,
and put on our todo to move to am 1.6 for Squid-2.6? (should probably
have the old versions of automake and autoconf in parallell then, for
maintenance of Squid-2.5)
Or should we bite and jump to automake-1.6 + newer autoconf?
Note: If we upgrade then we need to keep the old autoconf version for a
while for Squid-2.4 maintenance reasons.
Regards
Henrik
Alexandre Duret-Lutz wrote:
>
> >>> "Robert" == Robert Collins <robert.collins@itdomain.com.au> writes:
>
> Robert> w/ Automake 1.5, we have the following bug report. In summary, the
> Robert> following shell code:
>
> Robert> am_aux_dir=`CDPATH=:; cd $ac_aux_dir && pwd`
>
> Robert> is not portable to MacOS X, and is causing a headache for folk building
> Robert> in the same dir tree. Can we change it to
>
> Robert> am_aux_dir=`unset CDPATH; cd $ac_aux_dir && pwd` ?
>
> Robert> or has this been already been reported and fixed in 1.6?
>
> Yes, it's fixed in 1.6.
>
> `unset' is not portable.
>
> Recent Autoconf versions will set or unset CDPATH as
> appropriate, so the above line has been rewritten as
>
> am_aux_dir=`cd $ac_aux_dir && pwd`
>
> In Makefiles, however, you still have to fiddle with CDPATH.
> Automake 1.6 uses
>
> CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd somewhere && pwd
>
> --
> Alexandre Duret-Lutz
Received on Thu Apr 18 2002 - 11:08:18 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:15:12 MST