| [cdt-dev] Cygwin path problem |
|
Hi All, I don’t know whether
my problem and Mike’s problem is the same. But I am too facing similar
kind of issue. On my machine I am not able
to compile C program. It gives me ‘Build error (Exec error:%1 is not a valid Win32
application.)’. When I debugged I found that while exec it is crashing as pid
returned is -1. Is it related to env object which is passed to the exec? I have
observed that on the other machines which can compile the programs have env
with all the variables listed in it. But on my machine it is only
‘PWD’ and ‘CWD’ variables in the env. Please guide me on this. Regards, Rekha ------------------------------------------------------ Original Message Date: Fri, 30 Mar 2007
10:43:09 +0100 From: "Michael
Wrighton" <mikew@xxxxxxxxxxxxxx> Subject: [cdt-dev] Cygwin
path problem To: < Message-ID:
<B2E1E83609061340B13D8A7B0FF9F7C2048B7D@xxxxxxxxxxxxxxxxxxxxxxx> Content-Type: text/plain;
charset="us-ascii" Please let me know if I have
targeted the wrong mailing list but I have come across an issue when trying to
run the latest CDT on windows/cygwin and just wanted to find out if anyone can
tell me what the problem could be. To make it clear, I have two
windows machines both running eclipse 3.3 M6, latest CDT, cygwin and java
1.5.0_06. One of the machines works fine and can build cygwin projects, the
other one cannot locate any of the tools. I have debugged it and found that the
root of the problem is that ProcessFactory.exec() throws
an exception every time it's called, so is unable to run regedit to get the
cygwin path. What I cannot understand is why this is happening (I believe it's
actually the Spawner.exec0() native method that is failing). If anyone's
familiar with this code I would be grateful for any insight. I'm
hoping/expecting it's something silly in my environment. Thanks, Mike W |