public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steve Litster <litster@xtal200.harvard.edu>
To: help-gcc@gnu.org
Subject: build problem
Date: Thu, 02 Dec 1999 08:08:00 -0000	[thread overview]
Message-ID: <38469985.7006C8C3@crystal.harvard.edu> (raw)

I'm trying to build the full egcs system on a Dec Alpha running Tru64
Unix.

The make bootstrap runs Ok until it gives teh following


cc:Severe /usr/include/syms.h, line 125:cannot find file
<cmplrs/stsupport.h> specified in #include directive. (noinclfile)


I've tried changing locations of the stsupport.h file, but then a
message come back that mips-tfile.c cannot be compiled.

Am I missing something obvious?

Cheers,

Steve.


WARNING: multiple messages have this Message-ID
From: Steve Litster <litster@xtal200.harvard.edu>
To: help-gcc@gnu.org
Subject: build problem
Date: Fri, 31 Dec 1999 22:24:00 -0000	[thread overview]
Message-ID: <38469985.7006C8C3@crystal.harvard.edu> (raw)
Message-ID: <19991231222400.uSlgbORiuehrzxtjcNV3ApPWxowdEjJnhgZCfLNMvVQ@z> (raw)

I'm trying to build the full egcs system on a Dec Alpha running Tru64
Unix.

The make bootstrap runs Ok until it gives teh following


cc:Severe /usr/include/syms.h, line 125:cannot find file
<cmplrs/stsupport.h> specified in #include directive. (noinclfile)


I've tried changing locations of the stsupport.h file, but then a
message come back that mips-tfile.c cannot be compiled.

Am I missing something obvious?

Cheers,

Steve.


             reply	other threads:[~1999-12-02  8:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-02  8:08 Steve Litster [this message]
1999-12-31 22:24 ` Steve Litster

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=38469985.7006C8C3@crystal.harvard.edu \
    --to=litster@xtal200.harvard.edu \
    --cc=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).