Re: [Chicken-users] pathname tests

[Brandon J. Van Every]

felix winkelmann wrote:
> On 7/19/06, Brandon J. Van Every <address@hidden> wrote:
> > >
> > >  csc -s x.scm
> > >  csi -nbq x                   (should load x.[so|dll])
> >
> > This fails under both a MSYS shell and a Windows command prompt.  The
> > following is from the command prompt attempt. I have no idea how the
> > substring "Chickein" is obtained, as I haven't misspelled anything.
> >
> >
> > E:\Program Files\Chicken\bin>csc -s E:\devel\x.scm
> > 'E:Program' is not recognized as an internal or external command,
> > operable program or batch file.
> > *** Shell command terminated with exit status 1: "E:Program
> > FilesChickein/chicke
> > n" E:\devel\x.scm -output-file E:\devel\x.c -dynamic -feature
> > chicken-compile-sh
> > ared -quiet
> >
> > Looking at my csc.scm, the directory backslashes are not escaped.  Also
> > there are forward slashes where directories were tacked on.  I'm going
> > to guess that both of these things are bad.
>
> Yep, the latter is probably my bad. Somewhere in csc.scm.in I'm
> using slashes instead of "make-pathname". I'll check.

The forward slash is now gone, that's an improvement.  But missing 
backslashes and the weird "Chickein" misspelling remain.  I can't find 
"Chickein" anywhere in the source tree with grep, so it must be 
generated somehow.  The error now:

Brandon J. Van address@hidden /e/Program Files/chicken/bin
$ csc -s x.scm
'E:Program' is not recognized as an internal or external command,
operable program or batch file.
*** Shell command terminated with exit status 1: "E:Program 
FilesChickein\chicken" x.scm -output-file x.c -dynamic -feature 
chicken-compile-shared -quiet



Cheers,
Brandon Van Every