This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Uninstalling GCC


I use multiple versions of gcc under cygwin since the release of 3.0,
and currently have 4 or 5 versions installed (all of them in /usr/local
except the cygwin standard version):

2.95.3:
$ gcc -v
Reading specs from /usr/lib/gcc-lib/i686-pc-cygwin/2.95.3-5/specs
gcc version 2.95.3-5 (cygwin special)

3.0.4:
$ gcc3 -v
Reading specs from /usr/local/lib/gcc-lib/i686-pc-cygwin/3.0.4/specs
Configured with: ./configure --verbose --enable-threads=win32
--with-system-zlib --disable-nls --disable-shared --enable-static
--with-gnu-as --with-gnu-ld --program-suffix=3 --enable-languages=c,c++
--disable-libgcj --disable-checking --enable-sjlj-exceptions
--enable-haifa
Thread model: win32
gcc version 3.0.4

3.1:
$ gcc31 -v
Reading specs from /usr/local/lib/gcc-lib/i686-pc-cygwin/3.1/specs
Configured with: ../configure --disable-shared --enable-languages=c,c++
--enable-static --with-gnu-as --with-gnu-ld --disable-multilib
--enable-threads=win32 --disable-libgcj --disable-win32-registry
--disable-checking --disable-nls --with-system-zlib --verbose
Thread model: win32
gcc version 3.1

3.2 (experimental):
$ gcc32 -v
Reading specs from /usr/local/lib/gcc-lib/i686-pc-cygwin/3.2/specs
Configured with: ../configure --disable-shared --enable-languages=c,c++
--enable-static --with-gnu-as --with-gnu-ld --disable-multilib
--enable-threads=win32 --disable-libgcj --disable-win32-registry
--disable-checking --disable-nls --with-system-zlib --verbose
--with-ld=/usr/local/bin/sk_ld.exe --with-as=/usr/local/bin/sk_as.exe :
(reconfigured)
Thread model: win32
gcc version 3.2 20020520 (experimental)

I have no problems with any of them, and removing one of them is as
simple as deleting the gcc,g++,c++ etc. binaries from /usr/local/bin,
then removing the directory from /usr/local/lib/gcc-lib/i686-pc-cygwin/
that belongs to the version of gcc you wish to remove, and then
installing the new one to replace all documentation with the new stuff
and any headers and libraries installed by it.

I do the same with many versions of binutils since I have cron jobs to
cvs update and build and replace the binaries with the latest versions
every time a new snapshot is made or I specifically ask it to :-)

While I don't recommend that you take such an extreme route as I do, you
can safely put gcc in /usr/local, and it will save you a lot of trouble
since all the paths are already set ;)

CM

PS: 2.95.3 is by no means 'vintage' yet, since it is still very widely
used.

-----Original Message-----
From: gcc-owner@gcc.gnu.org [mailto:gcc-owner@gcc.gnu.org] On Behalf Of
Keen Wayne A Contr AFRL/MNGG
Sent: 20 May 2002 14:00
To: 'gcc@gcc.gnu.org'
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



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]