From: Jeffrey A Law <law@cygnus.com>
To: Aaron Jackson <jackson@negril.msrce.howard.edu>
Cc: egcs@cygnus.com
Subject: Re: More Ultrix problems...
Date: Tue, 04 Nov 1997 19:30:00 -0000 [thread overview]
Message-ID: <14826.878700090@hurl.cygnus.com> (raw)
In-Reply-To: <9711030141.AA03526@negril.msrce.howard.edu>
In message < 9711030141.AA03526@negril.msrce.howard.edu >you write:
> After adding -fsjlj-exceptions to the CFLAGS otions in the gcc makefile,
> I was able to get egcs to build. But it died while building the runtime
> libraries (see below). Anybody know what might have caused this type of
> error?
I don't see an error, except that is just said Error code 1.
Sometimes this happens with lame shells and/or make programs.
However, I don't see an "if" statement of the form that normally
triggers this kind of problem (it tends to happen when the if
statement evaluates false, and there is no else clause for the
if statement).
jeff
prev parent reply other threads:[~1997-11-04 19:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-02 17:50 Aaron Jackson
1997-11-04 19:30 ` Jeffrey A Law [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=14826.878700090@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=jackson@negril.msrce.howard.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).