A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2002-January/019230.html below:

Large file system support in 2.1.2 (was Re: [Python-Dev] release for 2.1.2, plus 2.2.1...)

Large file system support in 2.1.2 (was Re: [Python-Dev] release for 2.1.2, plus 2.2.1...) Large file system support in 2.1.2 (was Re: [Python-Dev] release for 2.1.2, plus 2.2.1...)Neal Norwitz neal@metaslash.com
Sun, 06 Jan 2002 19:27:31 -0500
"Barry A. Warsaw" wrote:
> 
> Okay, I'm totally confuggled now.  Let's boil this down.  Take this
> simple program:
> 
> -------------------- snip snip --------------------/tmp/foo.sh
> #! /bin/sh
> echo "OPT   = x${OPT}x"
> echo "CFLAGS= x${CFLAGS}x"
> -------------------- snip snip --------------------
> 
> and invoke it like:
> 
> % CFLAGS='one' OPT="two $CFLAGS" /tmp/foo.sh

I think the intent was to use single quotes for OPT='two $CFLAGS'.
(You could also do OPT="two \$CFLAGS".)  This will pass the string
"$CFLAGS" in OPT, not the value of the shell variable $CFLAGS.

While your shell script will print out: OPT   = xtwo $CFLAGSx
This is ok since it will/should get expanded properly in the Makefile.

Or I've totally missed the point too. :-)

Neal



RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4