From: Craig Burley <burley@gnu.org>
To: karipid@mae.cornell.edu
Cc: egcs@cygnus.com
Subject: Re: build of egcs-1.0.2 on mips-sgi-irix5.3
Date: Sat, 11 Apr 1998 22:11:00 -0000 [thread overview]
Message-ID: <199804120506.BAA21746@melange.gnu.org> (raw)
In-Reply-To: <199804092009.QAA00470@scotch.mae.cornell.edu>
>make options: LANGUAGES="c c++ g77"
>
>comments:
>
>Overall, the gcc and g++ look good, I think. I have no idea what
>happened to g77, but the results are terrible. I did not have this
>happen with version 1.0.1. I'm pretty sure others have built 1.0.2
>and did not have this many failures with g77.
I suggest the failures are mostly due to your not actually building
g77 in the first place!
In particular, if you can't find an executable file named "f771"
in your build tree after the build, then g77 ain't there, and
the g77 (and libf2c) tests will, naturally, fail.
Note that LANGUAGES takes a list of *languages*, not *compilers*,
so if you re-try your effort (nearly from scratch, I'm afraid) with
this line instead, you might see better results:
LANGUAGES="c c++ f77"
(Note the "f77" instead of "g77".)
tq vm, (burley)
prev parent reply other threads:[~1998-04-11 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-10 0:39 Daniel Karipides
1998-04-10 12:35 ` Jeffrey A Law
1998-04-11 22:11 ` Craig Burley [this message]
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=199804120506.BAA21746@melange.gnu.org \
--to=burley@gnu.org \
--cc=egcs@cygnus.com \
--cc=karipid@mae.cornell.edu \
/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).