search

ppradeepk / golangide

Automatically exported from code.google.com/p/golangide
0 stars 0 forks source link

Can't run a .go file. Run (Ctrl+F5) gives "process failed to start" #53

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Changed the settings win64.env to my go installation
2. Open hello.go
3. Click the Run button

What is the expected output? What do you see instead?
Expect to see formatted output from hello.go.  Instead I get

<action id="Run" cmd="${TARGETPATH}" args="${TARGETARGS}">
<start=" " 
workdir="C:/dean/src/go/misc"/>
<error msg="process failed to start" 
/>
</action>


What version of the product are you using? On what operating system?

X10 1.5625
Windows 7 pro 64-bit
go1.0.1.windows-amd64.zip

Please provide any additional information below.

Goclipse works.

Original issue reported on code.google.com by dean.w.s...@gmail.com on 6 May 2012 at 1:53

GoogleCodeExporter commented 9 years ago 
please download liteide x11 beta3 or high.

Original comment by Visua...@gmail.com on 7 May 2012 at 12:11

GoogleCodeExporter commented 9 years ago 
x11 beta3 has the same problem.

Original comment by dean.w.s...@gmail.com on 7 May 2012 at 9:47

GoogleCodeExporter commented 9 years ago 
liteide faq : liteenv setup
Options -> LiteEnv or Welcome: Options -> LiteEnv -> win64.env

change GOROOT to your computer GOROOT path, restart liteide and select win64 
env.

#win64 environment

GOROOT=c:\go-w64
GOARCH=amd64
GOOS=windows

PATH=%GOROOT%\bin;%PATH%

LITEIDE_GDB=gdb64
LITEIDE_MAKE=mingw32-make
LITEIDE_TERM=%COMSPEC%
LITEIDE_TERMARGS=
LITEIDE_EXEC=%COMSPEC%
LITEIDE_EXECOPT=/k

Original comment by Visua...@gmail.com on 9 May 2012 at 12:10

GoogleCodeExporter commented 9 years ago 
I had already set the environment as you describe.  I reinstalled LiteIDE and 
set the environment again.  Got the same results:

<action id="Run" workdir="C:/dean/src/go/misc" cmd="$(TARGETPATH)" 
args="$(TARGETARGS)">

>  $(TARGETARGS)

> error process failed to start.

</action>


You need a better message than "process failed to start".

Original comment by dean.w.s...@gmail.com on 9 May 2012 at 12:46

GoogleCodeExporter commented 9 years ago 
this is go.exe not find, check liteenv setup

Original comment by Visua...@gmail.com on 15 May 2012 at 3:10

GoogleCodeExporter commented 9 years ago 
I had the same problem! In addition to all what is adviced here, please also 
verify that your project's main file is called "main.go" and the first sttement 
is "package main", not any other package and the function "main" is present. I 
am not sure if this is a problem with the IDE or Go, but fixing my program as 
adviced here 
http://stackoverflow.com/questions/11949007/go-cannot-compile-hello-world-window
s/ , solved the problem in this LiteIDE also.

Original comment by alex.mur...@gmail.com on 14 Aug 2012 at 10:09

GoogleCodeExporter commented 9 years ago 
But, yeah, the <action id="Build" cmd="$(GO)" args="build $(BUILDARGS)" 
work="D:/Programming/Go/src/mytest"> thing constantly littering the console is 
VERY annoying.

Original comment by alex.mur...@gmail.com on 14 Aug 2012 at 10:37

GoogleCodeExporter commented 9 years ago 
Hello,

just had the same problem. In the path to the project was a foldername with 
space ('Google Drive'). Moved the project folder and now it works.

cheers, Heiner

Original comment by schreibh...@gmail.com on 7 Dec 2012 at 11:21

GoogleCodeExporter commented 9 years ago 
Still the same problem, on mac. Should this have been released..?

Original comment by Remi.d...@gmail.com on 15 Jan 2013 at 9:44

GoogleCodeExporter commented 9 years ago 
Maybe you should display more information about the error?
"process failed to start" --- reason?

Original comment by Rider...@gmail.com on 23 Jan 2014 at 1:33

GoogleCodeExporter commented 9 years ago 
That was all the information I got.  This thread is so old it can be closed 
out.  I've long since given up on this IDE.

Original comment by dean.w.s...@gmail.com on 23 Jan 2014 at 3:01

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
There is no problem with LiteIDE. It could be better and pick the correct 
GOROOT but it doesn't. The default values don't work for everyone so here is 
the solution:

①Go to "Preferences..." > "LiteEnv" and double click the file that matches 
your system (for example most OS X would be "darwin64.env") or you can change 
the "system.env" which is the one used by default.

②You need to setup GOROOT correctly in the file just opened.
If you don't know what to set: go to the terminal and do "echo $GOROOT", if 
nothing appears (recent versions of Go don't need GOROOT so the result will be 
empty) then do "go env GOROOT"

③Finally, when writing code you should make sure the correct configuration is 
being picked up. Select the same environment edited (in step 1) in the 
Environment toolbar

See the attached screenshot (or the link) so everything becomes clearer.
http://i62.tinypic.com/35ndn4g.png

Original comment by nach...@gmail.com on 22 Jan 2015 at 8:03

Attachments:

GoogleCodeExporter commented 9 years ago 
I've carefully followed all the instructions from #13 but it's not working.  
Still getting the error 

"process failed to start" 

when building.

Using version  X26 on Mac OSX along with go1.4.1

Original comment by mpe...@gmail.com on 28 Jan 2015 at 4:59

GoogleCodeExporter commented 9 years ago 
I have the same problem on Mac OS X with go1.4. My GOROOT is set to 
usr/local/go in Darwin64 local and I still get "process failed to start"

Original comment by tmani...@gmail.com on 18 Mar 2015 at 6:56

GoogleCodeExporter commented 9 years ago 
I was having the same problem and it turns out it was because the file I was 
trying to run wasn't in the main package. Once I changed my package declaration 
to "package main" everything worked. Not saying this is the problem everyone is 
having, but some might.

Maybe there could be a better error message? When I use the go command directly 
I get:

  go run: cannot run non-main package

Original comment by SimonMor...@gmail.com on 28 Mar 2015 at 5:01