--- In solarisx86@yahoogroups.com, "J.J.Bailey" <jjb@b...> wrote:
> > Another thing I just had to do with Solaris 9 4/04:
> > GCC 3.3.3 needs to be rebuilt to aknowledge the huge differences
in some
> > of Solaris 9 4/04 headers (hey, SSE are allowed now, so I'm not
> > complaining :-)
> >
> > Sample problem (I actually had exactly the same with some other
tarballs):
> >
> > g++ -O2 -DNDEBUG -Wall -W -Wshadow -Wpointer-arith -Wwrite-strings
> > -pedantic -ffor-scope bonnie++.cpp -o bonnie++ bon_io.o bon_file.o
> > bon_time.o semaphore.o forkit.o bon_suid.o
> > In file included from /usr/include/sys/reg.h:13,
> > from /usr/include/sys/regset.h:24,
> > from /usr/include/sys/ucontext.h:21,
> > from /usr/include/sys/signal.h:240,
> > from /usr/include/signal.h:27,
> > from bonnie++.cpp:43:
> > /usr/include/ia32/sys/reg.h:300: error: parse error before `[' token
> > /usr/include/ia32/sys/reg.h:301: error: parse error before `[' token
> > /usr/include/ia32/sys/reg.h:331: error: parse error before `[' token
> > make: *** [bonnie++] Error 1
> >
> > I know it can theorically happen with GCC, but it's the first time
I see
> > such a difference!
>
> Ah, so it isn't just me! ;-) Both the problems I describe below are
> new problems in 04/04.
>
> When building mozilla-1.7b with gcc-3.3.3, gcc barks about some of the
> enum defs in:
>
> /usr/include/gnome-vfs-2.0/libgnomevfs/gnome-vfs-file-info.h
> /usr/include/gnome-vfs-2.0/libgnomevfs/gnome-vfs-xfer.h
>
> Some of the entries' last definitions are followed by commas. gcc
> considers that a syntax error.
>
> When building bluefish-0.12, configure gets confused finding getopt
> strncasecmp, and strncmp.
>
>
This look like similar problems with Solaris 10 and gcc.
If you have a local gcc3 say you installed in your gcc in
/usr/local/gcc3 than try running
/usr/local/gcc3/lib/gcc-lib/i386-pc-solaris2.10/3.3.3/install-tools/
mkheaders
IF your install is on 2.10 directory.
Solaris 9 users and blastwave might have to run
/opt/csw/gcc3/lib/gcc-lib/i386-pc-solaris2.9/3.3.3/install-tools/mkheaders
Depending on the MU date of coarse.
This should fix gcc include headers. At least it works for me.
---Bob