[C++-SIG] CXX problems on SGI

[Paul F. Dubois]

Danger, Will Robinson. Not serious, but:

The init method of a module has to stay extern "C" or Python won't load it.

> -----Original Message-----
> From: c++-sig-admin at python.org [mailto:c++-sig-admin at python.org]On
> Behalf Of Barry Scott
> Sent: Thursday, September 14, 2000 4:42 AM
> To: 'Marc Poinot'; Geoffrey Furnish
> Cc: Python/C++ SIG
> Subject: RE: [C++-SIG] CXX problems on SGI
>
>
> [6] CXX developers fix CXX to work with SGI, etc, compiler
>
> One of the aims of the changes that went into 5.0b was to get the
> code base using std c++ syntax. I use gcc 2.95.2 on FreeBSD and
> Microsoft Visual C++ 6.0 SP4 to test the CXX code out.
>
> Both compile and run CXX except for FreeBSD that the exception
> handling does not work in one case.
>
> I suspect the root cause of the problems you see is the work to
> use std c++ syntax. That is where the extern "C" stuff came from.
>
> What happends if you change all the extern "C" to extern "C++"?
>
> If this fixes the problem for you we can add condition code to
> support none std c++ compilers into the CXX code base.
>
> 		Barry
>
>
> -----Original Message-----
> From: Marc Poinot [mailto:Marc.Poinot at onera.fr]
> Sent: 12 September 2000 13:58
> To: Geoffrey Furnish
> Cc: Marc Poinot; Python/C++ SIG
> Subject: Re: [C++-SIG] CXX problems on SGI
>
>
> *BEWARE* (this is a constructive email ;)
>
> Geoffrey Furnish wrote:
> >
> > Marc Poinot writes:
> >  >
> >  > What kind of compilers are you using ?
> >  >
> Again: Are you using something else than the KAI C++ ?
> I cannot compile CXX 5.0b on any of our compilers
> here (SGI,DEC,NEC,CRAY,FUJITSU, and gcc).
> We have Python on all these platforms, and Python is
> used for our C++/Fortran application.
> I was using CXX 4.2 for some Pythons optional extensions, but
> now, what can I do ?
>
> [0] Stay with CXX 4.2
> [1] Leave CXX and move to another kind of C++ extensions
> [2] Hack into CXX to make it run, do it again for each release
> [3] Wait the the next good release of compiler
> [4] Buy the KAI C++ for every platform
> [5] Change to Perl^H^H^H^H Bourne shell scripts
>
> Sure your C++ is an high level one, but what if you're
> the only one to be able to compile it ? Who's going to use CXX ?
> Maybe the right platform, even if the C++ is not ISO compliant,
> is to take a g++ subset of ISO C++ and allow some simpler code.
>
> > Looks to me like you have a bug in your compiler.  Can you upgrade?
> > Which version of the SGI compiler are you using?  Latest is
> > 7.3.something.
> >
> Even without the try/catch blocks into the externs, the compiler fails.
> According to our support, all of our compilers are up-to-date
> (SGI is 7.30).
>
> Ok, now I'm starting with [2], but I'm afraid this will lead to something
> like a parallel branch :(  (even simulated by pre-processing).
> The first step I'm going to do is to add a makefile with options for every
> of our
> platforms, split headers into seperate files per each class, move
> inlines to
> a
> compiled bodies and extend some tests (see you next year ;)
>
> Marcvs [alias I have no access to the CVS server, but I can work on a CVS
>         workspace tarball and send it back to you?]
>
> _______________________________________________
> C++-SIG maillist  -  C++-SIG at python.org
> http://www.python.org/mailman/listinfo/c++-sig
>
> _______________________________________________
> C++-SIG maillist  -  C++-SIG at python.org
> http://www.python.org/mailman/listinfo/c++-sig
>