Problems with libg++ compile on 4.0D

From: Ann Cantelow <cantelow_at_athena.csdco.com>
Date: Thu, 12 Mar 1998 12:24:00 -0700 (MST)

Hi. I'm trying to compile libg++ 2.8.0 after our upgrade to 4.0D and I'm
running into this error:

In file included from fstream.h:30,
                 from fstream.cc:34:
iostream.h:92: parse error before `__extension__'
iostream.h:210: parse error before `__extension__'
*** Exit 1
Stop.
*** Exit 1
Stop.

Has anyone seen this? I can't seem to find anything in the archives
mentioning this problem.

The libio/iostream.h file has this code in it leading up to line 92:

    ostream& write(const char *s, streamsize n);
    ostream& write(const unsigned char *s, streamsize n)
      { return write((const char*)s, n);}
    ostream& write(const signed char *s, streamsize n)
      { return write((const char*)s, n);}
    ostream& write(const void *s, streamsize n)
      { return write((const char*)s, n);}
    ostream& seekp(streampos);
    ostream& seekp(streamoff, _seek_dir);
    streampos tellp();
    ostream& form(const char *format ...);
    ostream& vform(const char *format, _IO_va_list args);

    ostream& operator<<(char c);
    ostream& operator<<(unsigned char c) { return (*this) << (char)c; }
    ostream& operator<<(signed char c) { return (*this) << (char)c; }
    ostream& operator<<(const char *s);
    ostream& operator<<(const unsigned char *s)
        { return (*this) << (const char*)s; }
    ostream& operator<<(const signed char *s)
        { return (*this) << (const char*)s; }
    ostream& operator<<(const void *p);
    ostream& operator<<(int n);
    ostream& operator<<(unsigned int n);
    ostream& operator<<(long n);
    ostream& operator<<(unsigned long n);
#if defined(__GNUC__) /* This is line 92 */
    __extension__ ostream& operator<<(long long n);
    __extension__ ostream& operator<<(unsigned long long n);
#endif
    ostream& operator<<(short n) {return operator<<((int)n);}
    ostream& operator<<(unsigned short n) {return operator<<((unsigned
int)n);}

I'm afraid I'm pretty unskilled in C. Does anyone see the parse error
referred to? I'm using 'make all "CC=gcc -O2"', after successfully
installing gcc 2.7.2.3 under 4.0D, except that there was one warning of a
"type mismatch in implicit declaration for built-in function `strlen'" (or
maybe it was strcpy). Second question- should I worry about that message?


 Many thanks, and I promise to summarize.


Ann Cantelow
cantelow_at_athena.csdco.com
Received on Thu Mar 12 1998 - 20:24:21 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:37 NZDT