[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-users] Chicken-setup 2.3 fails on Cygwin
From: |
Patrick Brannan |
Subject: |
Re: [Chicken-users] Chicken-setup 2.3 fails on Cygwin |
Date: |
Wed, 22 Mar 2006 08:10:44 -0600 |
This works for chicken-setup.scm create-directiory on cygwin:
(define create-directory
(if (and windows (not (eq? (build-platform) 'cygwin)))
(lambda (dir)
(when (run-verbose) (printf " creating directory `~a'`~a' ~%~!" dir ))
(foreign-lambda void "create_directory" c-string))
(lambda (dir)
(when (run-verbose) (printf " creating directory `~a'~%~!" dir))
(system* "mkdir -p ~a" dir) ) ) )
Maybe, if others think it is ok, it should be added to chicken-setup.scm.
Pat
On 3/22/06, Patrick Brannan <address@hidden> wrote:
> I can get this to duplicate as well. I wondered for a while why this
> doesn't happen with the MINGW build and took a look at the
> create-directory lambda in chicken-setup. I noticed that in the
> verbose output we were not getting an echo of the create-directory
> function. So I changed the function to this:
>
> (define create-directory
> (if windows
> (lambda (dir)
> (when (run-verbose) (printf " win: creating directory `~a'~%~!" dir))
> (foreign-lambda void "create_directory" c-string))
> (lambda (dir)
> (when (run-verbose) (printf " creating directory `~a'~%~!" dir))
> (system* "mkdir -p ~a" dir) ) ) )
>
> Sure enough it spits out "win: creating directory `numbers.egg.dir'"
>
> I would guess that it should use mkdir on cygwin. The question is how
> to figure out if we are on cygwin.
>
> Pat
>
> On 3/21/06, John Cowan <address@hidden> wrote:
> > Matthew Welland scripsit:
> > > No idea if this is related but I had a similar problem where if the
> > > current
> > > directory had a space in the path chicken-setup would fail. Running
> > > chicken-setup in a location where the path was free of spaces worked fine.
> >
> > That's one of the classic problems with porting Unix programs to
> > Cygwin. Of course, it's a problem in principle on Unix too, but
> > it doesn't come up as often. Usually a discreet use of double-quotes
> > around the $PATH variable solves the problem.
> >
> > --
> > XQuery Blueberry DOM John Cowan
> > Entity parser dot-com address@hidden
> > Abstract schemata http://www.ap.org
> > XPointer errata http://www.ccil.org/~cowan
> > Infoset Unicode BOM --Richard Tobin
> >
> >
> > _______________________________________________
> > Chicken-users mailing list
> > address@hidden
> > http://lists.nongnu.org/mailman/listinfo/chicken-users
> >
>