From: "Rupert Wood" <me@rupey.net>
To: "'wp'" <qwertygd@wp.pl>
Cc: <gcc-help@gcc.gnu.org>
Subject: RE: Help required to upgrade gcc
Date: Thu, 03 Apr 2008 11:16:00 -0000 [thread overview]
Message-ID: <01e601c89577$edd78330$c9868990$@net> (raw)
In-Reply-To: <007301c89575$299c23b0$7800a8c0@ntbkmm>
Marek wrote:
> 3. ./configure
> 4. make
> 5. make install
This will have built a new version of GCC and installed it in /usr/local/bin. You can use the new version if you add that directory to your path. You may also need to ensure /usr/local/lib is in your LD_LIBRARY_PATH. Note that the GCC install instructions recommend building GCC outside the source directory, i.e. you shouldn't be using "./configure" in step 3 - see http://gcc.gnu.org/install/configure.html
To overwrite your existing GCC system you need to use "--prefix=/usr" on the compile line or similar. Probably the best thing to do would be to look at the entire configure line from your currently installed GCC (use "gcc -v") and copy / paste that. However are you sure you want to do that? If you have existing C++ libraries built with the old compiler, for example, these will very likely be incompatible with the new C++ compiler. It may be easier to leave the new version of GCC in /usr/local and run it from there, or start again with a fresh Linux install if you do really want to update your system compiler.
Rup.
next prev parent reply other threads:[~2008-04-03 10:46 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
2008-04-03 11:16 ` Rupert Wood [this message]
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='01e601c89577$edd78330$c9868990$@net' \
--to=me@rupey.net \
--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).