From: Jeffrey A Law <law@cygnus.com>
To: kkaempf@progis.de (Klaus Kaempf)
Cc: gregg@eoeml.gtri.gatech.edu, joel@OARcorp.com, egcs@cygnus.com
Subject: Re: EGCS-970929 and GNAT-3.10p?
Date: Thu, 16 Oct 1997 08:31:00 -0000 [thread overview]
Message-ID: <9679.877015923@hurl.cygnus.com> (raw)
In-Reply-To: <9710161026.AA23945@progis.de>
In message < 9710161026.AA23945@progis.de >you write:
> >
> > I started poking at gnat-3.10p with egcs a short while ago -- I got
> > gnat1 and gnattools built on the PA. It then died building the
> > library due to a buglet in the gcc-2.7.2 PA binaries provided by
> > the GNAT folks.
> >
> AFAIK the openVMS/Alpha backend of gcc is based on gnat-4.x and may
> not run with gnat-3.x at all. This may be true for other backends too.
It wouldn't suprise me if there's numerous numerous it doesn't work
with.
jeff
next prev parent reply other threads:[~1997-10-16 8:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-08 14:14 Greg Galloway
1997-10-08 21:19 ` Jeffrey A Law
1997-10-09 9:26 ` Joel Sherrill
1997-10-09 16:31 ` Jim Wilson
1997-10-15 21:43 ` Jeffrey A Law
1997-10-16 2:35 ` Klaus Kaempf
1997-10-16 8:31 ` Jeffrey A Law [this message]
1997-10-16 12:53 ` Jim Wilson
1997-10-16 15:19 ` Jeffrey A Law
1997-10-16 15:19 ` Joel Sherrill
1997-10-16 15:19 ` Joel Sherrill
1997-10-16 15:19 ` Jeffrey A Law
1997-10-16 21:51 ` Richard Henderson
1997-10-16 23:09 ` egcs-971016 Oleg Krivosheev
1997-10-17 14:36 ` egcs-971016 Jeffrey A Law
1997-10-17 5:26 ` EGCS-970929 and GNAT-3.10p? Joel Sherrill
1997-10-17 15:05 ` Toon Moene
1997-10-18 8:45 ` Joel Sherrill
1997-10-23 13:54 ` Toon Moene
1997-10-23 12:49 ` Joel Sherrill
1997-10-09 16:12 ` Jim Wilson
1997-10-09 9:26 Greg Galloway
1997-10-09 16:12 ` Jim Wilson
1997-10-15 20:16 ` Jeffrey A Law
1997-10-16 12:50 ` Jim Wilson
1997-10-16 12:50 Greg Galloway
1997-10-16 12:53 ` 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=9679.877015923@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=gregg@eoeml.gtri.gatech.edu \
--cc=joel@OARcorp.com \
--cc=kkaempf@progis.de \
/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).