Help building gcc

[gaf at blu.org (Jerry Feldman)]

On Thu, 12 Aug 2004 12:20:12 -0400
miah <jjohnson at sunrise-linux.com> wrote:

> At the very least you wouldn't be using the AIX C compiler which may
> have who knows how many GNU incompatibilities.  So 2.9 may be a good
> place to start with building a newer release of GCC.  I'd really
> suggest starting that way, then once you have your gcc <currentver>
> build your toolchain.  Also, google is my friend.
I've been into the sources of the AIX C compiler as the parser was used
for Lint under Tru64 Unix as part of the OSF1 project. 

However, the most important things to do with C sources are to make sure
they are highly C-89 compatible. AFAIK, AIX C does have an ANSI
compatibility mode. The biggest inconsistencies will be with C++ as gcc
3.0 implemented the new standard where the 2.9x compilers did not. 

The other things to be concerned about is the Unix standards themselves.
Most Unix systems support one or more of the several Unix standards,
such as SVID, Unix95 and Unix98. These are done through numerous feature
switches in the header files. 

On Tru64, the only reason we used GCC is where we had GNU tools that
were tied to the GCC environment. I think that things like BISON and
FLEX needed GCC. 

-- 
Jerry Feldman <gaf at blu.org>
Boston Linux and Unix user group
http://www.blu.org PGP key id:C5061EA9
PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.blu.org/pipermail/discuss/attachments/20040812/64026de0/attachment.sig>