public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Ian Baker" <lists@oakengrove.com>
To: "'wp'" <qwertygd@wp.pl>, <gcc-help@gcc.gnu.org>
Subject: RE: Help required to upgrade gcc
Date: Thu, 03 Apr 2008 10:46:00 -0000	[thread overview]
Message-ID: <000a01c89576$2de9b670$89bd2350$@com> (raw)
In-Reply-To: <007301c89575$299c23b0$7800a8c0@ntbkmm>

If you type 'which gcc'
You will see that it reports /usr/bin/gcc
 
This file is a link, under Mandriva, to /etc/alternatives/gcc
Which in turn is a link to the 4.0 version of gcc that you are using. 

If you delete /usr/bin/gcc then it should expose the 4.2 version that you
have installed, depending on where you installed it

Best

Ian

> -----Original Message-----
> From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org] On
> Behalf Of wp
> Sent: 03 April 2008 11:26
> To: gcc-help@gcc.gnu.org
> Subject: Help required to upgrade gcc
> 
> I am facing issuue in upgrading of gcc-4.0.1 to gcc-4.2.0 My distro
> Mandriva
> 2006Not getting any error while compilation, but ggc --version still
> showing
> the version 4.0.1 only
> after compilation.
> Steps we have followed is
> 1. downloded gcc-4.2.0.tar from gnu.org
> 2. Untar the file
> 3. ./configure
> 4. make
> 5. make install
> We did not get a single error in the above steps.
> 
> what I do wrong ??Thanks for any helpMarek


  reply	other threads:[~2008-04-03 10:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1207217294.28834.ezmlm@gcc.gnu.org>
2008-04-03 10:34 ` wp
2008-04-03 10:46   ` Ian Baker [this message]
2008-04-03 11:16   ` Rupert Wood
2008-04-03 12:31     ` Tom Browder
2008-04-03 18:49       ` wp
2008-04-03 21:06         ` Tom Browder
2007-05-28  9:37 Santhosh1 C
2007-05-30  1:09 ` Ian Lance Taylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000a01c89576$2de9b670$89bd2350$@com' \
    --to=lists@oakengrove.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=qwertygd@wp.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).