public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Laurent Marzullo" <laurent.marzullo@be.sema.com>
To: <gcc-help@gcc.gnu.org>
Subject: building gcc-2.95.2 does not build libstdc++ directory!!!!
Date: Thu, 22 Feb 2001 06:31:00 -0000	[thread overview]
Message-ID: <NEBBLDHMLKKHEAKFKMIHIELDCDAA.laurent.marzullo@be.sema.com> (raw)

Hello,

I've download gcc-2.95.2.tar.gz
I've download libstdc++-2.91.tar.gz

And try to build like this:

	> cd /usr/src/redhat/SOURCES
	> gzip -dc gcc-2.95.2.tar.gz | tar xf -
	> cd gcc-2.95
	> gzip -dc libstdc++-2.91.tar.gz | tar xf -

Now, I've got libstdc++ and libstdc++-2.91 into gcc-2.95.2
directory.

	> mv libstdc++ libstdc++-v2
	> ln -s libstdc++-2.91 libstdc++

Then ...

	> cd /usr/src/redhat/BUILD/
	> mkdir gcc-2.95
	> cd gcc-2.95.2
	> ../../SOURCES/gcc-2.95.2/configure --enable-languages=c++

	....

	> make bootstrap

	...

	> make install


And ... libstdc++ was not build !!! There's no /usr/local/include/g++-v3
directory anywhere on my system. And header file of the library (
iterator.h, fstream, etc) are only present in gcc-2.95.2 SOURCES dir 

Why the library was not build ?
Anyone as any help please ?

                 reply	other threads:[~2001-02-22  6:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=NEBBLDHMLKKHEAKFKMIHIELDCDAA.laurent.marzullo@be.sema.com \
    --to=laurent.marzullo@be.sema.com \
    --cc=gcc-help@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).