Re: [Chicken-users] Chicken 2.41 tarball on Cygwin doesn't handle whitespace in pathnames

[John Cowan]

Brandon J. Van Every scripsit:

> I believe Chicken contains no support for whitespace in pathnames.  
> Cygwin is the only "known good" ./configure build on Windows.  
> ./configure with MinGW + MSYS dies on the ever-incorrect posixunix.c.  
> MSVC built with makefile.vc has different internal handling: it does not 
> define C_USE_C_DEFAULTS, does not use chicken-defaults.h, and relies on 
> the CHICKEN_HOME environment variable for path information.  So, I don't 
> see that this has ever worked for anyone, or could have worked.  Rather, 
> the problem has been avoided.  Relying on the Cygwin environment is one 
> way to avoid it, and relying on CHICKEN_HOME is another.

All you say is true; however, the problem needs to be fixed on all
platforms.  Unix (including Cygwin) pathnames don't usually contain
spaces, but they *can* contain them; any character except NUL is
legal in a Unix pathname.

-- 
John Cowan  address@hidden   http://ccil.org/~cowan
It's the old, old story.  Droid meets droid.  Droid becomes chameleon.
Droid loses chameleon, chameleon becomes blob, droid gets blob back
again.  It's a classic tale.  --Kryten, Red Dwarf