7 messages in com.perforce.jammingJam binaries for win95| From | Sent On | Attachments |
|---|---|---|
| Ian ...@compuserve.com | 05 Sep 1997 00:38 | |
| jste...@kdc-tvcom.com jstewart@kdc-tvcom.com | 05 Sep 1997 05:25 | |
| Ian ...@compuserve.com | 05 Sep 1997 06:38 | |
| Coli...@bird.fu.is.saga-u.ac.jp | 09 Sep 1997 01:46 | |
| "# Cowham, Robert Exchange CowhamR@logica.com | 09 Sep 1997 01:58 | |
| Ian ...@compuserve.com | 09 Sep 1997 05:28 | |
| Ian ...@compuserve.com | 10 Sep 1997 07:13 | .c |
| Subject: | Jam binaries for win95![]() |
|---|---|
| From: | Ian ...@compuserve.com (Ian ...@compuserve.com) |
| Date: | 09/09/1997 05:28:48 AM |
| List: | com.perforce.jamming |
Colin Peters wrote:
Not trying to make any excuses but... ok, I am making excuses.
Hey, no excuses needed; you modified Jam for Mingw32, I'm looking for something different. Thanks to you for Mingw32.
One of the nice things about Jam is that you have the source code and = it is easy to modify, so anything you don't like about it, you can change=
=2E
This is my real problem: I can't rebuild on win95 with VC5.0.
Actually I can build jam0.exe, but when it runs to build jambase.c and jam.exe it usually locks my DOS box, and certainly does some strange things on the way. I guess there's some difference between win32 on 95 a= nd NT, when using the spawnvp() call to execute the actions, which causes th= e problem. I can build jam.exe manually, but it does the same sort of thin= g when it runs for real. The exe's seem to work OK until asked to execute some actions.
Ian





.c