From: Michael Eager <eager@eagercon.com>
To: Kunal Sachdeva <kunal_gcc@yahoo.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Upgrade from 2.9 to 3.x?
Date: Mon, 12 May 2003 15:15:00 -0000 [thread overview]
Message-ID: <3EBFBAA4.7030703@eagercon.com> (raw)
In-Reply-To: <20030512134636.51724.qmail@web20502.mail.yahoo.com>
Kunal Sachdeva wrote:
> Hello All,
> I am quite new to the software development under
> Linux. For my source code I am using GCC2.96 and since
> its not the latest and also not the stable versions, I
> would like to update it to 3.x. I have no idea how can
> I do that.
Most C code will not require any changes to compile with GCC-3.x.
C++ code may need to be modified. Most common is to add
"using namespace std;" at the beginning of the source.
--
Michael Eager Eager Consulting eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
next prev parent reply other threads:[~2003-05-12 15:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 13:47 Kunal Sachdeva
2003-05-12 15:15 ` Michael Eager [this message]
2003-05-12 16:03 ` Kunal Sachdeva
2003-05-12 16:56 ` Eric Christopher
2003-05-12 17:56 ` Scott Robert Ladd
2003-05-12 18:10 ` Gerald Pfeifer
2003-05-12 23:33 ` Scott Robert Ladd
2003-05-13 0:39 ` Joe Buck
2003-05-13 2:24 ` Scott Robert Ladd
2003-05-13 1:14 Richard Kenner
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=3EBFBAA4.7030703@eagercon.com \
--to=eager@eagercon.com \
--cc=gcc@gcc.gnu.org \
--cc=kunal_gcc@yahoo.com \
/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).