bug-m4
[Top][All Lists]
Advanced

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

Re: Working os/2 configuratie


From: Gary V. Vaughan
Subject: Re: Working os/2 configuratie
Date: Tue, 22 Apr 2008 02:36:22 -0400

Hi Eric,

On 21 Apr 2008, at 22:29, Eric Blake wrote:
According to Gary V. Vaughan on 4/21/2008 5:36 PM:
|> +if test "${M4MODPATH+set}" = set ; then
|> +  M4MODPATH="@abs_top_builddir@/modules:$M4MODPATH"
|> +else
|> +  M4MODPATH="@abs_top_builddir@/modules"
|> +fi
|
| M4MODPATH="@abs_top_builddir@/modules${M4MODPATH+:$M4MODPATH}"

I thought about that, but is it portable to all shells?

The : is part of the expansion, so using M4MODPATH="stuff${M4MODPATH +stuff}"
is no different to 'if test "${M4MODPATH+stuff}" = stuff'

Then again, maybe I was just misreading
http://www.gnu.org/software/autoconf/manual/autoconf.html#Shell-Substitutions
about restrictions against non-portable ${a:+b}.


Yeah, shell variable expansions are far too numerous to hold in your head
all at the same time! :-)

Cheers,
        Gary
--
  ())_.              Email me: address@hidden
  ( '/           Read my blog: http://blog.azazil.net
  / )=         ...and my book: http://sources.redhat.com/autobook
`(_~)_




Attachment: PGP.sig
Description: This is a digitally signed message part


reply via email to

[Prev in Thread] Current Thread [Next in Thread]