Re: GCC Compiler for AIX 5.3

From: Andrew Elmore (aelmore_at_INTERWOVEN.COM)
Date: 06/27/05

  • Next message: Drew T: "cdrom burn HOWTO for AIX?"
    Date:         Mon, 27 Jun 2005 12:23:53 -0700
    To: aix-l@Princeton.EDU
    
    

    On Mon, Jun 27, 2005 at 01:30:39PM -0400, Sebastien Roy wrote:
    > We have a big problem ;) No it's not a system crash ... we do a
    > migration to AIX 5.3 ML02 from AIX 5.2ML06 last week and since that the
    > gcc compiler don't work anymore. I try to compile something (apache
    > 1.xx , php 4.x and some others GNU Utilities...) and we got always the
    > same error...
    >
    > /usr/include/pthread.h:652: error: parse error before '*' token
    > /usr/include/pthread.h:655: error: parse error before '*' token
    > /usr/include/pthread.h:658: error: parse error before '*' token
    > /usr/include/pthread.h:661: error: parse error before '*' token
    > /usr/include/pthread.h:664: error: parse error before '*' token
    > /usr/include/pthread.h:672: error: parse error before '*' token
    > /usr/include/pthread.h:675: error: parse error before '*' token
    > /usr/include/pthread.h:678: error: parse error before '*' token
    > /usr/include/pthread.h:681: error: parse error before '*' token
    > /usr/include/pthread.h:689: error: parse error before '*' token
    > /usr/include/pthread.h:693: error: parse error before '*' token
    > /usr/include/pthread.h:696: error: parse error before '*' token

    [...]

    > So anyone know what we can do to resolv that problem?

    The problem is that IBM changed the header files in such a way that gcc
    doesn't like them. Note that there's a step in the gcc build process
    that creates a customized version of headers to work with the particular
    OS version on the build machine, which probably isn't AIX 5.3. Most
    likely, the header files in /usr/include are combining badly with gcc's
    idea of the corrected version.

    You don't say which version of gcc you're using, but a very good bet is
    to get the gcc source code and build it yourself; the fixincludes step
    will have a fighting chance to Do The Right Thing for 5.3 ML2.

    Oh, and let IBM know that you want gcc to work better on AIX.

    regards,
    Andrew

    --
      Andrew Elmore                    Interwoven, Incorporated
      Staff Engineer                   Enterprise Content Management
    

  • Next message: Drew T: "cdrom burn HOWTO for AIX?"

    Relevant Pages

    • Re: SCOs infringing files list
      ... > The last file seems to be a modified version of the 0.96bp2 header files ... > needed in order to work with the new gcc release (searching for that filename ... This does seem to be the case - from an FAQ that H J Lu posted about that time: ... FAQ about gcc (how to compile program under Linux) ...
      (Linux-Kernel)
    • Fw: include file errors
      ... "Installing GCC automatically creates and installs the fixed header files, ... Subject: include file errors ...
      (Fedora)
    • Re: Preprocessor gcc and override
      ... > header files. ... If the directory dir is a standard system ... Directories named with -I are searched first, as the snippit of the info ... GCC uses the first file that matches. ...
      (comp.lang.cpp)
    • Re: migration from Solaris 8 to 9 = g++ compile problems (threads)
      ... there is no problem in running Solaris 8 binaries under ... In case of GCC, however, you may run into following problem: ... - Header files are subject to be changed during releases. ...
      (comp.unix.solaris)
    • Re: Linux C header files on Windows?
      ... >> Well I have thought about copying the linux header files but I ... As for a 'Windows build of the Linux gcc' I'm not sure I ...
      (comp.lang.c)