Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: brobecker@gnat.com, mec.gnu@mindspring.com, ac131313@redhat.com,
	gdb@sources.redhat.com
Subject: Re: A.R. Index for GDB version 6.1.91_20040719
Date: Tue, 20 Jul 2004 04:33:00 -0000	[thread overview]
Message-ID: <9003-Tue20Jul2004072615+0300-eliz@gnu.org> (raw)
In-Reply-To: <20040719221402.2A8F64B104@berman.michael-chastain.com> (mec.gnu@mindspring.com)

> Date: Mon, 19 Jul 2004 18:14:02 -0400 (EDT)
> From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
> 
> (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).

All this does happen on MS-DOS, and therefore gnat_ada.gpr_in is not
good because the generated gnat_ada.gpr will overwrite it.

> 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".

Not really accurate: even if the file _is_ used, we only care that its
name is unique after 8.3 truncation (plus some other requirements).
This is because all DOS file-related system calls silently truncate
file names to 8.3 limits before they start to actually act on the
file.

> 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.

And if the test suite worked for the DJGPP port, these two files would
actually work, as explained above, because when the test opens
null_record.adb, say, it will happily find null_rec.adb instead.

Note that files that are part of the configury stuff are actually
accessed on MS-DOS, since the configure script is run in its entirety,
as on Unix.


  parent reply	other threads:[~2004-07-20  4:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-19 22:16 Michael Elizabeth Chastain
2004-07-20  0:30 ` Daniel Jacobowitz
2004-07-20 10:27   ` Eli Zaretskii
2004-07-20  4:33 ` Eli Zaretskii [this message]
  -- 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=9003-Tue20Jul2004072615+0300-eliz@gnu.org \
    --to=eliz@gnu.org \
    --cc=ac131313@redhat.com \
    --cc=brobecker@gnat.com \
    --cc=gdb@sources.redhat.com \
    --cc=mec.gnu@mindspring.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