public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Henning <phenning@cs.uiowa.edu>
To: egcs@cygnus.com
Subject: Native build on mips-sgi-irix6.2 and DejaGNU question
Date: Wed, 29 Oct 1997 09:50:00 -0000	[thread overview]
Message-ID: <199710291750.LAA17781@server.cs.uiowa.edu> (raw)

I have built egcs-971023 twice now on mips-sgi-irix6.2
host/target. The first time was using a "gcc 2.7.2.3" I had built a
while ago, and that built fairly cleanly.

I then tried building with the SGI C compiler (v6.2), making sure that
none of the gcc tools were available.  My comments about the build are
attached below.  Should the top-level make assume that we are building
with gcc and thus try to build gcc/f before building the stage 1
compiler?  Also, there seems to be a "hidden" dependency on gperf;
should that be there?

Okay, now for the really ignant question.  I have dejagnu-1.3, but the
libio tests go looking for "standard.exp", which I don't have.  Any
suggestions? 

Thanks,
Paul Henning			phenning@cs.uiowa.edu

             reply	other threads:[~1997-10-29  9:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-29  9:50 Paul Henning [this message]
1997-11-02 22:12 ` Jeffrey A Law

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=199710291750.LAA17781@server.cs.uiowa.edu \
    --to=phenning@cs.uiowa.edu \
    --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).