From: Robert Lipe <robertl@dgii.com>
To: Zack Weinberg <zack@rabi.phys.columbia.edu>
Cc: egcs@cygnus.com
Subject: Re: 970917 on mips-sgi-irix6.2, haifa disabled: many problems
Date: Wed, 01 Oct 1997 18:59:00 -0000 [thread overview]
Message-ID: <19971001205651.60151@dgii.com> (raw)
In-Reply-To: <199710012320.TAA15918@nutation.phys.columbia.edu>
> > Also, for cases (xcoff/elf, n32/64) where the compiler has
> >There aren't any mips ports that support both xcoff and elf
> I was thinking of SCO here, but actually, irix5 can do both coff
OpenServer generates both COFF and ELF. Not xcoff and ELF.
I do think the same situation applies, though. I build for cross-mips
and have to wait for about a billion cross libes to build that I don't
ever even use.
RJL
next prev parent reply other threads:[~1997-10-01 18:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3585.875432731@hurl.cygnus.com>
1997-09-30 20:53 ` Zack Weinberg
1997-09-30 21:16 ` Richard Henderson
1997-09-30 23:11 ` Jim Wilson
1997-10-01 16:21 ` Zack Weinberg
1997-10-01 18:59 ` Robert Lipe [this message]
1997-09-26 9:48 Mike Stump
[not found] <21969.875000931@hurl.cygnus.com>
1997-09-26 8:54 ` Kamil Iskra
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=19971001205651.60151@dgii.com \
--to=robertl@dgii.com \
--cc=egcs@cygnus.com \
--cc=zack@rabi.phys.columbia.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).