Re: Basic script problem

[Andreas Schwab]

"Al" <address@hidden> writes:

|> Im having a very annoying problem. Im using the macro ac_jni_include_dirs
|> from the gnu archive to determine the location of the Java includes
|> directories. Ill paste it below for convenience. The suggested usage is
|> 
|> JAVAC="javac"
|> AC_JNI_INCLUDE_DIR
|> for JNI_INCLUDE_DIR in $JNI_INCLUDE_DIRS
|> do
|>     CPPFLAGS="$CPPFLAGS -I$JNI_INCLUDE_DIR"
|> done
|> 
|> Now, Im using Cygwin on Windows 98 and 2k and it happens that in both cases
|> my java home is nestled in the awful C:\Program Files directory This causes
|> problems on 2k because CPPFLAGS comes out something like
|> 
|> -I/cygdrive/c/Program -IFiles/Java/include
|> 
|> , its alright on 98 as $JNI_INCLUDE_DIRS comes back with the short windows
|> paths, ie /cygdrive/c/Progra~1/...
|> 
|> I thought this could be dealt with simply by changing the macro to wrap each
|> path in double quotes, but that doesnt work. The above for loop the produces
|> something stupid like
|> 
|> -I" -I/cygdrive/c/Program -IFiles/Java/include
|> 
|> When I type the for loop into the shell directly with exactly the same value
|> of $JNI_INCLUDE_DIRS as is used during configuration, the loop works as you
|> would expect it to. Whats the deal with the diference running it via
|> configure?

The quote is only recognised as meta character when occuring literally,
but not when part of an expansion.  Unfortunately, I don't think your
problem can be solved, you'll have to preserve proper quoting all the way
down to the command invocation in the makefile.  Don't use filenames that
contain spaces.

Andreas.

-- 
Andreas Schwab, SuSE Labs, address@hidden
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."