X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <a07c15f00810310802u7c303a70n4768b7a2f0c9daaa@mail.gmail.com>
Date: Fri, 31 Oct 2008 10:02:11 -0500
From: "Nathan Thern" <nthern AT gmail DOT com>
To: "Mikael More" <mikael DOT more AT gmail DOT com>
Subject: Re: Gambit Cygwin package
Cc: gambit-list AT iro DOT umontreal DOT ca, cygwin AT cygwin DOT com
In-Reply-To: <6cc5c97b0810301824u60fddbaex46caf9e58173a78f@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <6cc5c97b0810301824u60fddbaex46caf9e58173a78f AT mail DOT gmail DOT com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Thu, Oct 30, 2008 at 8:24 PM, Mikael More <X AT X> wrote:
> Hi!
> Thank you for porting Gambit into Cygwin!
http://www.liquid.spod.org/~nthern/cygwin/

> Although, on my machine, I didn't get it running, neither the package
> (compile-file complains it can't start external process) nor the Gambit
> sources (compile-file and shell-command fire cmd.exe instead of /bin/sh,
> even though i updated COMSPEC and SHELL environment variables).
> I just wanted to check with you if you know how to get it going.
> Thanks!
>
> Mikael

Interesting. All my testing so far consisted of calling "gsc -link
foo.scm" to create c files and then compiling them with "gcc ...".
Plain old "gsc foo.scm" does indeed exhibit the behavior you
described. Are you able to run "gsc -link foo.scm"? If so, then I
would say you at least "got it running".

Not sure where the problem lies. Since the cygwin system call API is
POSIX compliant, I'm going to guess that it's a configuration script
problem. That is, I'm guessing that somewhere configure assumes
something like "if we have windows.h then without exception make all
system calls through cmd.exe". I'm looking in the source but haven't
found it yet.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/