----- Original Message ----- > On Sun, 22 Feb 2004, Igor Pechtchanski wrote: > > > On Mon, 23 Feb 2004, Alvyn Liang wrote: > > > > > I don't know if this is proper to place here. alright > > > the installation of g95 can make your former binary hided... > > > in > > > > > > $ cygcheck -srv > > > > > > I found these two message: > > > > > > Warning: d:\cygwin\tmp\g95\bin\cpp.exe hides d:\cygwin\bin\cpp.exe > > > Warning: d:\cygwin\tmp\g95\bin\gcc.exe hides d:\cygwin\bin\gcc.exe > > > > > > Just a note for ppl who stuck here, maybe someone will just like me > > > searching for a solution by searching engines > > > > > > the results just like the following > > > > > > $ gcc test1.c > > > gcc: installation problem, cannot exec `cc1': No such file or directory > > > > > > I think the cygwin will always remember the last time it execute some file, > > > so that unless you restart the console it will continue to find the old > > > successful one. > > > > > > Alvyn > > > > Cygwin does no such thing. > > ... but some shells may, though I doubt it's the case here. While you're > in the bash man page, read about the 'hash' builtin. > HTH, > Igor > > > Read up on the PATH environment variable: > > > > PAGER='less +1017' man bash > > > > You can change the PATH by using "export PATH=<somevalue>". You (or some > > script) probably prepended "/tmp/g95/bin" to your PATH. Starting a new > > shell sets PATH to its default value (not that simple, but close enough), > > which doesn't contain that directory.
thanks for your reply and... sorry for the misunderstanding.. i admit that I had appended a line on '.bashrc' to include the PATH PATH=/tmp/g95/bin:/tmp:$PATH because i want to test the g95, but I did not notice this may hide my orignal compilers and they does not follow the default route to find out the cc1.exe In the beginning I use g++ for some other task was fine, then I found out it could not find cc1.exe after I did something that's why i checked cygcheck I found out this happening and change the name of d:\cygwin\tmp\g95\bin\cpp.exe to _cpp.exe d:\cygwin\tmp\g95\bin\gcc.exe to _gcc.exe so that they will not block by compilation.. now I think everything should be fine... :) Can someone give me some suggestions where to place the lib and bin files? Now I am following the instructions of some page I found out before, the standard include of library is the following gcc -I<include library path> -c <sourcefile>.c and then gcc <sourcefile>.o -l<library name> this seems to be a more safe way to deal with things for example in GSL,. I use gcc app.o -lgsl -lgslcblas -lm gcc app.o -lgsl -lcblas -lm or gcc app.o -lgsl -lcblas -latlas -lm I always feel upset when I install a new library, because sometimes the problem only happends on the order of the syntax of commands. I have to struggle with the paths and includes, is there anyway that makes things easier? Or, is there any rule that we can all safely compile with most of the libraries? thanks in advance Alvyn > > > > FWIW, if you'd attached the output of "cygcheck -svr" to your message, > > instead of simply quoting choice bits from it, it would have helped > > confirm the above. > > Igor -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
