RE: Can't get libstdc++ completely installed on Solaris-

[Michael VanLoon <MichaelV at EDIFECS dot COM>]

Any additional insights?  I just tried to use gmake 3.78.1, and the results
are the same...  Just for reference, I have appended the error text to the
end of this message.

-----Original Message-----
From: Benjamin Kosnik [mailto:bkoz@cygnus.com]
Sent: Friday, November 12, 1999 12:22 AM
To: libstdc++@sourceware.cygnus.com
Subject: Re: Can't get libstdc++ completely installed on Solaris-

Tools used:
>> gcc v2.95.2 (and its stdlibc++)
>> gmake v3.77
>> bash v2.03.0(1)

>hmm. . . is gmake aliased to make, so that "make" actually calls gmake?
>(which I assume is GNU make)

[michaelv@sun1]/export1/libstdc++-2.90.6# make --version
GNU Make version 3.78.1, by Richard Stallman and Roland McGrath.
Built for sparc-sun-solaris2.6
[etc....]


Once again, Solaris 2.6 with Sun Workshop Pro 5.0 installed (but not being
used).  Trying to build libstdc++ 2.90.6.


Making install in math
gmake[1]: Entering directory `/export1/libstdc++-2.90.6/math'
gmake[2]: Entering directory `/export1/libstdc++-2.90.6/math'
gmake[2]: Nothing to be done for `install-exec-am'.
gmake[2]: Nothing to be done for `install-data-am'.
gmake[2]: Leaving directory `/export1/libstdc++-2.90.6/math'
gmake[1]: Leaving directory `/export1/libstdc++-2.90.6/math'
Making install in string
gmake[1]: Entering directory `/export1/libstdc++-2.90.6/string'
gmake[2]: Entering directory `/export1/libstdc++-2.90.6/string'
gmake[2]: Nothing to be done for `install-exec-am'.
gmake[2]: Nothing to be done for `install-data-am'.
gmake[2]: Leaving directory `/export1/libstdc++-2.90.6/string'
gmake[1]: Leaving directory `/export1/libstdc++-2.90.6/string'
Making install in libio
gmake[1]: Entering directory `/export1/libstdc++-2.90.6/libio'
gmake[2]: Entering directory `/export1/libstdc++-2.90.6/libio'
gmake[2]: Nothing to be done for `install-exec-am'.
gmake[2]: Nothing to be done for `install-data-am'.
gmake[2]: Leaving directory `/export1/libstdc++-2.90.6/libio'
gmake[1]: Leaving directory `/export1/libstdc++-2.90.6/libio'
Making install in src
gmake[1]: Entering directory `/export1/libstdc++-2.90.6/src'
gmake[2]: Entering directory `/export1/libstdc++-2.90.6/src'
/bin/sh ../mkinstalldirs /usr/local/lib
/bin/sh ../libtool  --mode=install .././install-sh -c libstdc++.la
/usr/local/lib/libstdc++.la
.././install-sh -c .libs/libstdc++.so.3.0.0
/usr/local/lib/libstdc++.so.3.0.0
(cd /usr/local/lib && rm -f libstdc++.so.3 && ln -s libstdc++.so.3.0.0
libstdc++.so.3)
(cd /usr/local/lib && rm -f libstdc++.so && ln -s libstdc++.so.3.0.0
libstdc++.so)
chmod +x /usr/local/lib/libstdc++.so.3.0.0
.././install-sh -c .libs/libstdc++.lai /usr/local/lib/libstdc++.la
.././install-sh -c .libs/libstdc++.a /usr/local/lib/libstdc++.a
ranlib /usr/local/lib/libstdc++.a
chmod 644 /usr/local/lib/libstdc++.a
----------------------------------------------------------------------
Libraries have been installed in:
   /usr/local/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
     during execution
   - use the `-RLIBDIR' linker flag

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
gmake[2]: Nothing to be done for `install-data-am'.
gmake[2]: Leaving directory `/export1/libstdc++-2.90.6/src'
gmake[1]: *** No rule to make target `bits/basic_ios.h', needed by
`/usr/local/include/g++-v3/bits/basic_ios.h'.  Stop.
gmake[1]: Leaving directory `/export1/libstdc++-2.90.6/src'
gmake: *** [install-recursive] Error 1