From: "Jonathan L. Starr" <starr@belsoft.com>
To: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: gcc build
Date: Wed, 26 Jul 2000 07:51:00 -0000 [thread overview]
Message-ID: <397EFB5D.991A2AC2@belsoft.com> (raw)
I downloaded gcc-2.95.2-2-src.tar from a Cygnus mirror and tried
to build on a Sun OS4.1.3 system. The build failed because
directory libiberty in the directory above gcc (gcc-2.95.2-2)
was a link to ../common, which did not exist, and so some things
were considered missing (ostack.c, libiberty.a).
What do I need to do?
Thanks for any help.
--
-- Jonathan Starr
starr@belsoft.com
(781) 862-2343
next reply other threads:[~2000-07-26 7:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-26 7:51 Jonathan L. Starr [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-30 10:09 M R Swami Reddy
2009-03-30 10:28 ` Jason Pernito
2009-03-30 10:32 ` M R Swami Reddy
2009-03-30 10:37 ` M R Swami Reddy
[not found] <42258E26.60506@ing.uniroma2.it>
2005-03-02 14:50 ` Stephen Torri
2005-03-02 15:19 ` corey taylor
2000-08-08 11:56 Gcc build steve Waugh
2000-08-08 18:19 ` Alexandre Oliva
2000-07-22 13:29 gcc build Jonathan L. Starr
2000-07-26 11:05 ` Alexandre Oliva
2000-07-26 13:06 ` Jonathan L. Starr
2000-07-26 13:27 ` Alexandre Oliva
[not found] <Gregory>
[not found] ` <P.>
[not found] ` <Sherwood"'s>
[not found] ` <message>
[not found] ` <of>
[not found] ` <"Fri,>
[not found] ` <04>
[not found] ` <Feb>
[not found] ` <2000>
[not found] ` <09:33:58>
[not found] ` <-0800>
2000-02-04 9:31 ` GCC Build Gregory P. Sherwood
2000-02-06 19:06 ` Alexandre Oliva
2000-02-07 9:20 ` Gregory P. Sherwood
2000-04-01 0:00 ` Gregory P. Sherwood
2000-04-01 0:00 ` Alexandre Oliva
2000-04-01 0:00 ` Gregory P. Sherwood
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=397EFB5D.991A2AC2@belsoft.com \
--to=starr@belsoft.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).