public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Steven J. Madsen" <steve@moonglade.com>
To: egcs@cygnus.com
Subject: Building EGCS from scratch
Date: Mon, 08 Sep 1997 23:44:00 -0000	[thread overview]
Message-ID: <19970908234701.21678@calvin.moonglade.com> (raw)

I thought I knew what I was doing with all of this, but it seems that maybe
I don't after all.  The EGCS distribution has gotten so big at this point
that I'm at a loss where to start.  I can build GCC/G++ just fine, run the
tests and even install the compiler.  My problem is with everything else in
the top-level directory.

For example, it looks like there is a version of the standard C++ library
that is built.  However, when I'm doing this (on Linux, libc5, latest
everything), I get the following error while building libiostream.a:

make[1]: *** No rule to make target `stdio.list', needed by `libiostream.a'.

It seems that EGCS is sorely missing documentation on what needs to be built
for <foo> OS, and in what order.  I've been on the mailing list for a few
weeks now, and nothing of the sort has showed up in my mailbox.

Does anyone have any pointers?  (Sorry if this sounds frazzled, but I've
been spending the better part of my spare time the last two days trying to
grok this, and I'm just not getting it...)

-- 
Steve Madsen  <steve@moonglade.com>              PGP key available

             reply	other threads:[~1997-09-08 23:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-09-08 23:44 Steven J. Madsen [this message]
1997-09-09  7:50 ` Jeffrey A Law
1997-09-09 12:13 Mike Stump
1997-09-09 13:30 ` Joe Buck

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=19970908234701.21678@calvin.moonglade.com \
    --to=steve@moonglade.com \
    --cc=egcs@cygnus.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).