public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Brad Lucier <lucier@math.purdue.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: ada/6160: configure sets up bootstrap to build ada with too-old
Date: Thu, 04 Apr 2002 06:36:00 -0000	[thread overview]
Message-ID: <20020404143603.32302.qmail@sources.redhat.com> (raw)

The following reply was made to PR ada/6160; it has been noted by GNATS.

From: Brad Lucier <lucier@math.purdue.edu>
To: fw@deneb.enyo.de (Florian Weimer)
Cc: lucier@math.purdue.edu (Brad Lucier), gcc-gnats@gcc.gnu.org
Subject: Re: ada/6160: configure sets up bootstrap to build ada with too-old
Date: Thu, 4 Apr 2002 09:33:24 -0500 (EST)

 > 
 > Brad Lucier <lucier@math.purdue.edu> writes:
 > 
 > >> No, I don't think this is the case.  Do you have "." in your path?
 > >
 > > No.
 > 
 > Hmm.  What's the output of "gnatbind -v /dev/null" and 
 > "gnatgcc --verbose -x ada /dev/null"?
 > 
 
 dino01% gnatbind -v /dev/null
 
 GNATBIND 5.00w (20010924) Copyright 1995-2001 Free Software Foundation, Inc.
 
 Binding: null.ali
 gnatbind: Cannot find: null.ali
 dino01% gnatgcc --verbose -x ada /dev/null
 Reading specs from /usr/lib/gcc-lib//i386-redhat-linux/2.8.1/specs
 gcc version 2.8.1
  /usr/lib/gcc-lib//i386-redhat-linux/2.8.1/gnat1 -quiet -dumpbase null.ada /dev/null -o /tmp/cc1tXseL.s
 gnat1: Cannot find: null
 


             reply	other threads:[~2002-04-04 14:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-04  6:36 Brad Lucier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-04  6:36 Florian Weimer
2002-04-04  6:26 Florian Weimer
2002-04-04  6:26 Brad Lucier
2002-04-04  6:06 Brad Lucier
2002-04-04  5:26 Brad Lucier
2002-04-04  5:26 Florian Weimer

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=20020404143603.32302.qmail@sources.redhat.com \
    --to=lucier@math.purdue.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).