From: Ivan Martinez <ex08@kalman.iau.dtu.dk>
To: llewelly@dbritsch.dsl.xmission.com
Cc: gcc-help@gcc.gnu.org
Subject: Re: libstdc++ included?.
Date: Sun, 07 May 2000 10:17:00 -0000 [thread overview]
Message-ID: <3915C196.E11FD271@kalman.iau.dtu.dk> (raw)
In-Reply-To: <Pine.LNX.4.21.0005061444230.6355-100000@dbritsch.dsl.xmission.com>
llewelly@dbritsch.dsl.xmission.com wrote:
>
> On Sat, 6 May 2000, Ivan Martinez wrote:
>
> > Hello all,
>
> > How should I install this C++ distribution?.
>
> See http://gcc.gnu.org/install/index.html
>
I had a look at it and I saw that they are the typical compilation and
installaction instructions (./configure, make, make install), which I
already knew.
After downloading "GCC 2.95.2, gzip format, 1.6Meg" below "C++
distribution and updates to C++ distribution" in
"gcc.gnu.org/pub/gcc/releases/index.html", I untar it and get a
"gcc-2.95.2" directory. My problem is that under that directory there
isn't a "configure" file, so this package doesn't follow the common
installation way. There are three other directories, "gcc", "libio" and
"libstdc++". I look for "configure" with a file searcher without
success.
What am I doing wrong?. Many thanks.
> Keep in mind that the instructions are the same, whichever gcc source
> tarball you use; only the result differs. And you always get the C
> frontend.
>
> > Is there any configuration
> > file stablishing GCC's default include directories?. Thank you.
> >
--
Ivan Martinez (Rodriguez)
BEng in Software Engineering - MEng student
http://www.student.dtu.dk/~u990873
"Got fabes?"
next prev parent reply other threads:[~2000-05-07 10:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-06 10:47 Ivan Martinez
2000-05-06 13:54 ` llewelly
2000-05-07 10:17 ` Ivan Martinez [this message]
2000-05-07 20:07 ` llewelly
2000-05-08 5:23 Smith, Jack
2000-05-08 5:51 ` Pascal Bleser
2000-05-08 6:38 ` llewelly
2000-05-08 7:28 ` Martin v. Loewis
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=3915C196.E11FD271@kalman.iau.dtu.dk \
--to=ex08@kalman.iau.dtu.dk \
--cc=gcc-help@gcc.gnu.org \
--cc=llewelly@dbritsch.dsl.xmission.com \
/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).