[GRASS5] configure.in Wants testers...

Markus Neteler neteler at geog.uni-hannover.de
Tue Nov 28 12:27:21 EST 2000


On Tue, Nov 28, 2000 at 08:34:48AM -0800, Eric G . Miller wrote:
> On Tue, Nov 28, 2000 at 04:26:38PM +0700, Justin Hickey wrote:
> > I would have thought so but that is the current problem on my system.
> > The @SRCDIR@ variable is substituted with $(pwd) without executing the
> > pwd command. So it is now a make variable called pwd which is empty.
> > However, I did notice in that section of configure.in, that there are
> > brace brackets {} used for $top_srcdir but parenthesis () used for $pwd.
> > Could that be the problem? Just a wild guess.
> 
> Well here's my understanding:
> 
> foo=${bar}   # Perform variable expansion on "bar", put result in foo.
> 
> foo=$(bar)   # Execute "bar" in a subshell, put result in foo.
> 
> The $(cmd) syntax is supposed to be the portable equivalent of `cmd`,
> only special characters $ \ and * (I think) are not treated as
> "metacharacters".
> 
> This $(...) syntax is different from Makefile $(...) which apparently is
> variable substitution/expansion.
> 

Eric,

thanks for this info:

GRASS:~/ggg > foo=$(pwd); echo $foo
/home/neteler/ggg
GRASS:~/ggg > foo=${pwd}; echo $foo

GRASS:~/ggg > 

Another interesting hint for script programming!

BTW: Does anyone know a *good* book on script progamming containing such
"sekrets" and even more?

Regards
 Markus


---------------------------------------- 
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'



More information about the grass-dev mailing list