Hi Ian,
I think something about this should be in the FAQ. I will have to add
it. Unix, Linux, the GNU tools, etc. are happy with spaces in file
names. However, on a command line you would need quotes around the file
name to make it be seen as a single entry, rather than several. I used
to get similar troubles with older version of the MS stuff, but I think
they have gos their act together on this now.
I wonder why you find the problem "even if the offending entries have
quotes"? Quotes usually fix it.
Regards,
Steve
Ian Butler wrote:
Error 255 reported/discussed 30/9/03 thru 1/10/03
I found the solution to this one is simply to move the entry for mspgcc in
your PATH to the begining of the path environment variable. Basically it
appears to fall over if there is a space in any of the path entries
preceeding the 'mspgcc/bin' entry (even if the offending entries have
quotes"")
Hope this helps someone.
Regards,
Ian
