This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: Uninstalling GCC
- From: Keen Wayne A Contr AFRL/MNGG <keenwa at eglin dot af dot mil>
- To: "'gcc at gcc dot gnu dot org'" <gcc at gcc dot gnu dot org>
- Date: Mon, 20 May 2002 07:59:58 -0500
- Subject: RE: Uninstalling GCC
This is sort of a different question on the same topic. I build new
versions of gcc under
Cygwin, which has a default gcc that is 2.95.3 vintage. Now, it has been my
habit when
doing the build to have it placed in a unique directory, in my case one I
call /mygcc.
My thinking was that since its the only thing there, if I want to get rid of
it, it is easy
to do, and I do have to do "special" commands (i.e. run /mygcc/bin/g++ and
make sure
that I have a -L/mygcc/lib in the makefile) to run the new version, to
prevent conflicts.
For those who use the default /usr/local, is there some reason why the way I
am doing
things will cause me problems down the road?
Wayne Keen