how to build for solaris 8?

Bruno.Voigt@ic3s.de Bruno.Voigt@ic3s.de
Sat Apr 1 00:00:00 GMT 2000


Hi Phil,

yes thanks for your hint..now i could finisch the complete gcc/libstdst++
build

but compiling my app gives me now the following error.
the sam compilation worked before under sol7:

g++ -c   -I /usr/local/include/g++-v3 guregistry.cpp
In file included from /usr/local/include/g++-v3/bits/fpos.h:40,
                 from /usr/local/include/g++-v3/bits/char_traits.h:39,
                 from /usr/local/include/g++-v3/bits/std_string.h:40,
                 from /usr/local/include/g++-v3/string:2,
                 from guregistry.cpp:103:
/usr/local/include/g++-v3/bits/c++io.h:35: libio.h: No such file or directory
make: *** [guregistry.o] Error 1

What has changed?
I also discovered that there are two directories in /usr/local/include:
"g++-v3" and a "g++-3" path. That is the purpose of the  last? Where does it come from??

Bruno
--
Bruno.Voigt@ic3s.de  # IC3S AG # Tel. +49.4106.655.105 # Fax. +49.4106.4618
http://www.ic3s.de   # Mobile +49.700.686.00.686


                                                                                                                   
                    Phil Edwards                                                                                   
                    <pedwards@jaj        To:     Bruno.Voigt@ic3s.de                                               
                    .com>                cc:     libstdc++@sourceware.cygnus.com                                   
                                         Subject:     Re: how to build for solaris 8?                              
                    23.03.2000                                                                                     
                    22:23                                                                                          
                                                                                                                   
                                                                                                                   




> /export/home/bruno/bld-gcc/gcc/xgcc -B/export/home/bruno/bld-gcc/gcc/
> -B/usr/local/sparc-sun-solaris2.8/bin/ -DHAVE_CONFIG_H
> -I.  -I../../../../gcc-2.95.2/libstdc++/src -I.. -nostdinc++
> -I../../../../gcc-2.95.2/libstdc++ -I../../../../gcc-2.95.2/libstdc++/stl
> -I../libio -I../../../../gcc-2.95.2/libstdc++/libio
> -I../../../../gcc-2.95.2/libstdc++/config/cpu/sparc/sparc32
> -I../../../../gcc-2.95.2/libstdc++/config/solaris/solaris2.7
> -I/usr/local/include -D_GNU_SOURCE -fno-implicit-templates -Wall
> -Wno-format -W -Wwrite-strings -Winline -Werror -g -fhonor-std -g -O2
> -c  -fPIC -DPIC ../../../../gcc-2.95.2/libstdc++/src/stringMAIN.cc -o
> .libs/stringMAIN.lo
> cc1plus: warnings being treated as errors

That's the problem; it's warning about an inline statement that it can't
inline, and -Werror causes the warning to become an error.  Search for
the line

   WERROR = -Werror

in either (srcdir)/src/Makefile.in before you configure, or
(builddir)/src/Makefile after you configure.  There should only be a
single occurance.  Change it to

   WERROR =

You'll still get the warning, but it won't be a fatal error.

Phil







More information about the Libstdc++ mailing list