[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-users] windows shell problem
From: |
Ivan Raikov |
Subject: |
Re: [Chicken-users] windows shell problem |
Date: |
Tue, 06 Jan 2009 08:05:26 +0900 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) |
Ok, can you try passing "c:\home\chicken-trunk\bin\csi.exe" to the
Windows system(3) call? Perhaps it needs the full path to the
executable.
-Ivan
"felix winkelmann" <address@hidden> writes:
> The handling of backslashes as escaping characters is not the problem,
> it seems. If I pass this string (verbatim, just like it is printed here) to
> system(3):
>
> "c:\home\chicken-trunk\bin\csi" -bnq -e "(require-library setup-api)"
> -e "(import setup-api)" "c:\...some...path...\defstruct.setup"
>
> I get an error message that tells me that the program
>
> "c:\home\chicken-trunk\bin\csi" -bnq -e ""
- Re: [Chicken-users] windows shell problem, (continued)
- Re: [Chicken-users] windows shell problem, Thomas Chust, 2009/01/05
- Re: [Chicken-users] windows shell problem, Lars Nilsson, 2009/01/05
- Re: [Chicken-users] windows shell problem, felix winkelmann, 2009/01/05
- Re: [Chicken-users] windows shell problem, Tobia Conforto, 2009/01/05
- Re: [Chicken-users] windows shell problem, felix winkelmann, 2009/01/06
- Re: [Chicken-users] windows shell problem, John Cowan, 2009/01/05
- Re: [Chicken-users] windows shell problem, felix winkelmann, 2009/01/06
- Re: [Chicken-users] windows shell problem, Matthew Flatt, 2009/01/06
- Re: [Chicken-users] windows shell problem, felix winkelmann, 2009/01/06
- Re: [Chicken-users] windows shell problem, felix winkelmann, 2009/01/07
- Re: [Chicken-users] windows shell problem,
Ivan Raikov <=