gcc 2.95.1 HP-UX 11 problem

Jeffrey A Law law@cygnus.com
Fri Sep 3 02:52:00 GMT 1999


  In message <Pine.LNX.4.10.9909021700001.6512-100000@george.mmi>you write:
  > I actually got it to build with one hitch:
  > 
  >   ../../gcc-2.95.1/gcc/fixproto[266]: 7916 Memory fault(coredump)
  > 
  > although this did not interrupt the build.  When fixproto starts,
  > make issues the statement "Various warnings and error messages
  > from fixproto are normal." I doubt that a core dump falls within
  > normal warnings and errors, though.
This is definitely not normal.

As an aside, we should find some way to redirect all the error messages
from fixproto somewhere.  Both so that they can be reviewed from time to
time and to help clean up the build messages -- it's too tough right now
to follow what's happening and determine if something went wrong.

  > Anyway, a good deal of include file processing happened before
  > fixproto crashed, no more afterward, though the build continued.
  > It went on to install and seemed to work, at first.  However, the
  > following code, when compiled with the resulting g++, causes a
  > slew of compile-time errors:
  > 
  > //#include <string>
  > #include <vector>
  > 
  > int main()
  >     {
  > 
  >     return 0;
  >     }
  > 
  > The errors and warnings all have to do with size_t.  
  > Interestingly, if the first include directive is un-commented,
  > they all go away.  I strongly suspect this is because include
  > file processing was not completed or was elsehow munged up.
That is because no released version of gcc supports hpux11.

Get a development snapshot from gcc.gnu.org -- they include hpux11
support (32bit mode only though).  

The size_t problems are just the tip of the iceberg of problems
related to using gcc-2.95 (or earlier) versions of gcc on hpux11.

jeff


More information about the Gcc-help mailing list