Unable to build libstdc++-v3

Phil Edwards pedwards@disaster.jaj.com
Wed Aug 23 09:54:00 GMT 2000


On Wed, Aug 23, 2000 at 01:00:40PM +0200, Ronald Fischer wrote:
> I'm tryping to build gcc together with the libstdc++-v3 for Solaris 2.7.

Gotta warn you, it's not going to work.  Building under anything but Linux
right now isn't happening.  That should change soon.


> I did a configure, a gmake bootstrap and a gmake install. Everything
> worked without giving an error message. The last step installed the
> binaries, but did not put the include files to the installation
> directory and did not produce the lib.

Well, building libstdc++-v[23] should happen during the 'make bootstrap'
step, I believe.  Do you already have a working GCC installation?  If so,
'bootstrap' doesn't necessarily gain you anything; you should just be able
to use 'make all' to build the compiler and the selected libraries.


> grep: illegal option -- q
> Usage: grep -hblcnsviw pattern file . . .

Ah.  Crumbs.  The native Solaris grep doesn't take -q like POSIX says.
This is what happens when the native /usr/bin binaries are in the PATH
before the POSIX /usr/xpg4/bin binaries.  I'll try to adjust for that.


> I have no
> idea why it looks at a file "gnumake". I have gmake, and I have make,
> which is a symbolic link to gmake.

Some people install GNU make as gnumake, so it tries that name if it
can't find one of the others.  Since the grep failed, the configure script
decided that it had /not/, in fact, found anything.

What surprises me is that configure failed (using AC_MSG_ERROR) but the
top-level make kept right on going...


-- 
pedwards at disaster dot jaj dot com  |  pme at sources dot redhat dot com
devphil at several other less interesting addresses in various dot domains
The gods do not protect fools.  Fools are protected by more capable fools.


More information about the Libstdc++ mailing list