This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: A.R. Index for GDB version 6.1.91_20040719
- From: "Eli Zaretskii" <eliz at gnu dot org>
- To: Daniel Jacobowitz <drow at false dot org>
- Cc: mec dot gnu at mindspring dot com, brobecker at gnat dot com, ac131313 at redhat dot com, gdb at sources dot redhat dot com
- Date: Tue, 20 Jul 2004 07:31:07 +0200
- Subject: Re: A.R. Index for GDB version 6.1.91_20040719
- References: <20040719221402.2A8F64B104@berman.michael-chastain.com> <20040719221508.GA15872@nevyn.them.org>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> 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.