Home > Archive > Fortran > January 2008 > Re: binary of gcc and gfortran of snapshot 2008-0111 for windows is available for dow
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: binary of gcc and gfortran of snapshot 2008-0111 for windows is available for dow
|
|
|
|
"jacob navia" <jacob@nospam.com> wrote in message
news:fmd47t$vj6$1@aioe.org...
> When I start the compiler I get
>
> d:\gcc\bin>gcc hello.c
> gcc: CreateProcess: No such file or directory
>
> The compiler is unable to do anything. When called in
> standalone mode it works
>
> gcc
> d:\gcc\bin>gcc
> gcc: no input files
>
> But it doesn't do anything else
After re-examining your post, it seems you changed to the subdirectory
d:\gcc\bin to test the compiler immediately after you installed the binary.
Windows OS requires you logoff, and then login to make "new" environment
variables in effect. The compiler cannot work without proper environment
variables (Installer set the variables, but you need to login to make new
variables in effect).
If you try again, the compiler should work. It is not necessary to run the
compiler in the subdirectory d:\gcc\bin. You can run the compiler in any
subdirectory, for example, c:\temp.
Good luck.
| |
| Kenny McCormack 2008-01-13, 7:12 pm |
| In article <M1yij.2959$Y63.2359@trnddc03>, post <no-spam@equation.com> wrote:
....
>After re-examining your post, it seems you changed to the subdirectory
>d:\gcc\bin to test the compiler immediately after you installed the binary.
>Windows OS requires you logoff, and then login to make "new" environment
>variables in effect. The compiler cannot work without proper environment
>variables (Installer set the variables, but you need to login to make new
>variables in effect).
1) I'm amazed that the CLC topicality police aren't all over this
thread. Come on, guys! Cat got (all of) your tongues???
2) (OT, duh...) What you say above isn't true. Depending on exactly how
"the installer" set the variables, at most, all you should need to do is
open up a new CMD shell window.
|
|
|
|
|