68791 - fixing xpcom a bit to compile with upcoming gcc 3.0

Status: RESOLVED DUPLICATE of bug 63604

(Core :: XPCOM, defect)

Description

[Brendan Kehoe]

I'm slowly trying to massage mozilla so it will build successfully with the
current development copy of gcc, which is destined to come out as gcc 3.0. 

In xpcom/io/nsFileStream.h, I had to make it define these macros also for that
compiler:

NS_USING_NAMESPACE
NS_USING_STL

and explicitly not define NS_USE_PR_STDIO.  The lines modified were:

#if !defined(NS_USING_NAMESPACE) && (defined(__MWERKS__) || defined(XP_WIN) ||
(defined(__GNUC__) && defined(__GNUC_MINOR__) && __GNUC_MINOR__ >= 97))
#define NS_USING_NAMESPACE
#endif

#if !defined(NS_USING_STL) && (defined(__MWERKS__) || defined(XP_WIN) ||
(defined(__GNUC__) && defined(__GNUC_MINOR__) && __GNUC_MINOR__ >= 97))
#define NS_USING_STL
#endif

#if !defined(XP_MAC) && !defined(__KCC) && !(defined(__GNUC__) &&
defined(__GNUC_MINOR__) && __GNUC_MINOR__ >= 97)
// PR_STDOUT and PR_STDIN are fatal on Macintosh.  So for console i/o, we must
use the std
...etc...


You can get a snapshot of the compiler that will come up with the errors I've
seen from sourceware.cygnus.com in /pub/gcc, or via anonymous CVS (cf
http://gcc.gnu.org/).

Hope this helps,
B

Comment 1

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

There's already a bug on this, and it already has patches that allow building on
gcc 3 (modulo modifying some system headers that don't currently work with
-fno-exceptions, but that's being worked on by the libstdc++ folks).

*** This bug has been marked as a duplicate of 63604 ***

Comment 2

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

I suspect the fixes you mentioned were workarounds for the problems of
system headers not working with -fno-exceptions, right?  (What were the
errors?)  If so, that's simply a libstdc++ bug, and one that will certainly
be fixed before release.