home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!pipex!warwick!mrccrc!doc.ic.ac.uk!agate!usenet.ins.cwru.edu!magnus.acs.ohio-state.edu!zaphod.mps.ohio-state.edu!rpi!usc!sol.ctr.columbia.edu!spool.mu.edu!decwrl!elroy.jpl.nasa.gov!nntp-server.caltech.edu!eql.caltech.edu!rankin
- From: rankin@eql.caltech.edu (Pat Rankin)
- Newsgroups: vmsnet.misc
- Subject: Re: VMS GCC 2.3.1 around yet?
- Date: 10 Nov 1992 19:32 PDT
- Organization: California Institute of Technology
- Lines: 20
- Distribution: world
- Message-ID: <10NOV199219320303@eql.caltech.edu>
- References: <1992Nov9.112737.4679@dmc.com> <1992Nov9.201123.167@vedur.is>
- NNTP-Posting-Host: eql.caltech.edu
- News-Software: VAX/VMS VNEWS 1.41
-
- In article <1992Nov9.201123.167@vedur.is>,\
- gulli@vedur.is (Gunnlaugur Kristjansson) writes...
- > It's all there. I just took the distribution (GCC-2.3.1.tar.Z) and
- > Decompressed, Untared it. Then I ran VMSCONFIG.COM followed by
- > MAKE-GCC.COM. Moved the .EXE files to the proper dir and it worked.
- > I had GCC 2.2.2 and now I have GCC 2.3.1.
-
- You should build it at least twice, using the first one to rebuild
- itself. If you're not using an earlier version of GCC on the first pass,
- or if you're using a much older version of GCC, you should build it _three_
- times and with optimizations suppressed during the first build. Each new
- version often has additional optimizations that are useful in the compiler
- itself (you want compiles to run as quickly as possible don't you?) and the
- executable file(s) for the compiler won't benefit from them unless they've
- been built with the newer compiler...
-
- GCC 2.3.* has some annoying new warnings (under -Wparentheses, which
- is included as part of -Wall) that you may not like.
-
- Pat Rankin, rankin@eql.caltech.edu
-