From: "Eli Zaretskii" <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: mec.gnu@mindspring.com, brobecker@gnat.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 10:27:00 -0000 [thread overview]
Message-ID: <6654-Tue20Jul2004073107+0300-eliz@gnu.org> (raw)
In-Reply-To: <20040719221508.GA15872@nevyn.them.org> (message from Daniel Jacobowitz on Mon, 19 Jul 2004 18:15:09 -0400)
> Date: Mon, 19 Jul 2004 18:15:09 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> > (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).
>
> Correct; I don't know how configuration happens on msdos though.
Almost as it happens on Posix platforms: the configure script is run
(via ported Bash), except that the script and the configure scripts in
subdirectories are patched first to avoid file-naming problems and
problems with drive letters in file names. See
config/djgpp/djconfig.sh and config/djgpp/config.sed for the gory
details.
The upshot of all this is that any file that is part of the package
configury is actually accessed during the configure phase, and thus
cannot be renamed by fnchange.lst. If it cannot be renamed in the
repository (which is not the case with gnat_ada.gpr.in), the only
alternative is to rename it as part of the patches done by djconfig.sh
before it runs the configure script.
next prev parent reply other threads:[~2004-07-20 4:33 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 [this message]
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=6654-Tue20Jul2004073107+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--cc=ac131313@redhat.com \
--cc=brobecker@gnat.com \
--cc=drow@false.org \
--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