public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: lucier@math.purdue.edu
Cc: gcc@gcc.gnu.org
Subject: Re: Propose PR 6160 as high priority
Date: Mon, 08 Apr 2002 14:31:00 -0000	[thread overview]
Message-ID: <10204082114.AA03659@vlsi1.ultra.nyu.edu> (raw)

    That works for me.  But *something* should be done before release.

I don't understand the issue here.  The error message in that PR is
clear: the build was attempted with a version of GNAT that seems to
have been mis-installed since it was producing ALI files that the
corresponding gnatbind can't read.

It is neither practical nor necessarily desirable to test for every possible
way in which the GNAT installed on a system might be broken.  We could
have configure actually build and run an Ada program, but that's not necessary
to bootstrap GNAT since it uses lots of things that aren't needed to build
GNAT and it's not sufficient since it doesn't test the ability to properly
link both C and Ada.

             reply	other threads:[~2002-04-08 21:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-08 14:31 Richard Kenner [this message]
2002-04-08 14:36 ` Brad Lucier
  -- strict thread matches above, loose matches on Subject: below --
2002-04-15 13:43 Robert Dewar
2002-04-15 12:31 Robert Dewar
2002-04-15 13:27 ` Joseph S. Myers
2002-04-16 15:04   ` Florian Weimer
2002-04-28 22:27     ` Alexandre Oliva
2002-04-29  5:39       ` Florian Weimer
2002-04-29  6:50         ` Joseph S. Myers
2002-04-15 11:27 Richard Kenner
2002-04-08 14:45 Richard Kenner
2002-04-08 14:41 Richard Kenner
2002-04-15 11:04 ` Brad Lucier
2002-04-05 11:23 lucier
2002-04-08 13:55 ` Richard Henderson
2002-04-08 14:15   ` Brad Lucier

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=10204082114.AA03659@vlsi1.ultra.nyu.edu \
    --to=kenner@vlsi1.ultra.nyu.edu \
    --cc=gcc@gcc.gnu.org \
    --cc=lucier@math.purdue.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).