From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: brobecker@gnat.com, mec.gnu@mindspring.com
Cc: ac131313@redhat.com, eliz@gnu.org, gdb@sources.redhat.com
Subject: Re: A.R. Index for GDB version 6.1.91_20040719
Date: Mon, 19 Jul 2004 22:16:00 -0000 [thread overview]
Message-ID: <20040719221402.2A8F64B104@berman.michael-chastain.com> (raw)
joel> Back to Eli's problem: We need to have a name such that, after
joel> generation from configure, we end up with "gnat_ada.gpr" (fortunately,
joel> gnat_ada.gpr fits the 8+3 profile). Is that possible?
Yeah, I'm testing a patch right now.
gnat_ada.gpr.in is the default name, but AC_OUTPUT has a syntax for
specifying an explicit name, so I'm just using that. The new name will
be gnat_ada.gin if that's okay with daniel.
(At first I wanted to use gnat_ada.gpr_in, but then I thought:
what if someone configures in the source directory, and what if
configuration reaches down into testsuite/ even though testsuite/
does not actually run on msdos).
Also my understanding is: if the ms-dos port actually uses the file, the
name has to fit in 8.3. But if the ms-dos port does not use the file,
the name just has to be 8.3 unique with truncation, plus some other
requirements like "no more than one dot".
The test suite is not used on ms-dos so null_record.adb and
null_record.exp are fine. They get unpacked as null_rec.adb and
null_rec.exp, so they wouldn't actually work, but they survive the
process of unpacking the tarball.
Michael C
next reply other threads:[~2004-07-19 22:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 22:16 Michael Elizabeth Chastain [this message]
2004-07-20 0:30 ` Daniel Jacobowitz
2004-07-20 10:27 ` Eli Zaretskii
2004-07-20 4:33 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2004-07-19 22:13 Michael Elizabeth Chastain
2004-07-20 4:27 ` Eli Zaretskii
2004-07-19 21:04 Michael Elizabeth Chastain
2004-07-19 21:12 ` Daniel Jacobowitz
2004-07-19 21:19 ` Joel Brobecker
2004-07-19 3:25 Andrew Cagney
2004-07-19 3:54 ` Eli Zaretskii
2004-07-19 20:01 ` Eli Zaretskii
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=20040719221402.2A8F64B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=ac131313@redhat.com \
--cc=brobecker@gnat.com \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.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