Author rmt38
Recipients
Date 2006-01-06.05:46:15
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=1417949

> Why do you think that?  You will find that no autotooled
> package will build or install in directories with spaces

Perhaps I was not clear enough.  The problem is not that I 
am building in those directories, it is that the patch 
sets the PATH environment variable as a prefix to the 
compilation command (in the same line).  And on Windows, 
it is not uncommon for directories in Program Files and 
other directories with spaces in their names to be in the 
path.  This breaks the correctness of the command line and 
the execution of it.

Take another look at the erroneous command:

PATH=/usr/bin:.:/usr/local/bin:/mingw/bin:/bin:/c/WINDOWS/s
ystem32:/c/WINDOWS:/c/WINDOWS/System32/Wbem:/c/Program 
Files/ATI Technologies/ATI Control 
Panel:/c/PROGRA~1/COMMON~1/SONICS~1/:/c/Program 
Files/Common 
Files/Adobe/AGL:/usr/bin:/c/devkitpro/devkitarm/bin:. cc -
c -I -I./Include  -o Parser/acceler.x Parser/acceler.c

And the error:

/bin/sh: Files/ATI: No such file or directory
make: *** [Parser/acceler.x] Error 127

Hope this helps.
History
Date User Action Args
2007-08-23 15:44:21adminlinkissue1339673 messages
2007-08-23 15:44:21admincreate