Date: Thu, 02 Sep 2004 14:29:21 -0400
From: Andrew Cagney <cagney@gnu.org>
-XM_FILE= xm-go32.h
+DEPRECATED_XM_FILE= xm-go32.h
What exactly am I supposed to do here to avoid the danger of having
the DJGPP port nuked in the next release? Define GDBINIT_FILENAME,
CRLF_SOURCE_FILES, and DIRNAME_SEPARATOR on some header file(s)
conditioned by "#ifdef DJGPP"? It sounds silly to invent autoconf
tests for that when we know _exactly_ what system(s) will need that.
--- Begin Message ---
- From: "Eli Zaretskii" <eliz at gnu dot org>
- To: Andrew Cagney <cagney at gnu dot org>
- Cc: gdb at sources dot redhat dot com
- Date: Fri, 30 Jul 2004 21:06:40 +0300
- Subject: Re: [6.3] Drop xm-*.h from GDB - move to pure autoconf
- Delivery-date: Fri, 30 Jul 2004 14:35:54 -0400
- Envelope-to: cagney@gnu.org
- References: <410990A0.9040108@gnu.org> <1659-Fri30Jul2004143003+0300-eliz@gnu.org> <410A4BE4.5000306@gnu.org>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Fri, 30 Jul 2004 09:23:48 -0400
> From: Andrew Cagney <cagney@gnu.org>
>
> Check the contents of config/i386/xm-{cygwin,djgpp}.h. Instead of being
> detected by autoconf, those values are being hardwired. Easy to fix
Ah, that... Your message made it sound as if there's some inherent
problem that prevents autoconfiscation, so I was surprised.
Yes, it should be easy to fix, except for the gdb.ini part: if one
builds the DJGPP port on Windows or cross-compiles on Unix, the
filesystem will allow that name. So the test needs to be dependent on
the fact that a DJGPP port is being built, no matter what the
underlying OS has to say about .gdbinit.
Note that include/filenames.h has some constants similar to the `;' vs
`:' stuff, so maybe some of GDB sources could use the results of
autoconfiscation instead.
--- End Message ---