[NTLUG:Discuss] New gcc how-to
    Brian 
    brian-sender-67b5e0 at pongonova.net
       
    Sat Oct 12 15:00:52 CDT 2002
    
    
  
On Sat, Oct 12, 2002 at 01:59:01PM -0500, Geremy L. Hamlett wrote:
> OK, I am running a RedHat 7.3 box w/ gcc 2.96.  I would like to upgrade my 
> gcc to the new 3.2.  However, for what ever reason I do not want to use 
> the rpms.  RedHat installs their gcc in a diffrent place than the default 
> gcc souce install.  I have read that people install the second and just 
> leave the two gcc's on their system.  This sounds redundant to me and I 
> don't want two gcc's.  
Go ahead and install gcc-3.2 from the sources.  All of the configuration files are
saved in directories relative to your gcc-3.2 install, so they won't affect your
2.96 install.   Feel free to remove the 2.96 installation (using the appropriate
cryptic RPM commands) after you've thoroughly tested the new installation.
> First Question:  Can I just use the default install of gcc-3.2
I would recommend going this route, at least for your initial install.  Building gcc
is not a trivial process (nor is it rocket science), so you don't want to change too
many things at first (like installation directories).
> I know gcc is not something you really want to mess with unless you know 
> what you are doing.
You'll be doing yourself a favor by removing 2.96.
> I have not been able to find any documentation on the internet on how to 
> replace the 2.96 w/ anoter version. I know it has been done, 
> 
> Has anybody in the NTLUG done this?
Sure, I've done it, but not on a RH box.  I don't see why a RH install would be any
different than any other Linux flavor.
Truth be told, I'm sticking with my gcc-2.95-3 compiler until some of the kinks are
worked out of the 3.x compilers.
  --Brian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
Url : http://ntlug.org/pipermail/discuss/attachments/20021012/9049d67c/attachment.bin
    
    
More information about the Discuss
mailing list