Re: [patch] Deprecate XM_FILE and TM_FILE

[Andrew Cagney <cagney@gnu.org>]

[-- Attachment #1: Type: text/plain, Size: 556 bytes --]

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

I thought we discussed this with the attached.

Andrew


[-- Attachment #2: Attached Message --]
[-- Type: message/rfc822, Size: 3509 bytes --]

From: "Eli Zaretskii" <eliz@gnu.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: [6.3] Drop xm-*.h from GDB - move to pure autoconf
Date: Fri, 30 Jul 2004 21:06:40 +0300
Message-ID: <3791-Fri30Jul2004210638+0300-eliz@gnu.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.