From: "Michael Fischer" <fischermi@t-online.de>
To: <gdb-patches@sourceware.org>
Subject: AW: AW: AW: [PATCH] source.s: Fix problem handling windows like path with MinGW
Date: Sun, 18 Jun 2006 20:05:00 -0000 [thread overview]
Message-ID: <JLEAKDMELBINENLADICFEEFNCIAA.fischermi@t-online.de> (raw)
In-Reply-To: <umzca2qmo.fsf@gnu.org>
>> #ifdef __MSDOS__
>> #define CANT_FORK
>> #define GLOBAL_CURDIR
>> #endif
>>
>> #if defined(__MSDOS__) || defined(_WIN32) || defined(__OS2__) || defined
>> (__CYGWIN__)
>> #define DIRNAME_SEPARATOR ';'
>> #endif
>
>I think __CYGWIN__ should not be here. In fact, even _WIN32 should
>not trigger use of `;' unless __CYGWIN__ is not defined. Chris, is
>that right?
>
>Does anyone object to adding something like the above, provided that
>we are careful not to break Cygwin?
To make sure that we does not break Cygwin, perhaps we can use the following
check:
#if defined(__MSDOS__) || defined (__MINGW32__)
#define DIRNAME_SEPARATOR ';'
#endif
Only check for __MSDOS__ and __MINGW32__ in this case Cygwin
could not be affected.
Regards,
Michael
next prev parent reply other threads:[~2006-06-18 20:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <JLEAKDMELBINENLADICFIEFHCIAA.fischermi@t-online.de>
2006-06-18 3:24 ` Eli Zaretskii
2006-06-18 4:56 ` Masaki Muranaka
2006-06-18 9:03 ` AW: " Michael Fischer
2006-06-18 19:47 ` Eli Zaretskii
2006-06-18 20:05 ` Michael Fischer [this message]
2006-06-18 20:16 ` Christopher Faylor
2006-06-18 20:15 ` Christopher Faylor
2006-06-19 3:22 ` Eli Zaretskii
2006-06-20 20:27 ` Daniel Jacobowitz
2006-06-24 13:51 ` Eli Zaretskii
2006-06-18 19:47 ` Eli Zaretskii
2006-06-19 0:27 ` Masaki Muranaka
2006-06-19 3:14 ` Eli Zaretskii
2006-06-19 3:38 ` Masaki Muranaka
2006-06-20 20:24 ` Daniel Jacobowitz
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=JLEAKDMELBINENLADICFEEFNCIAA.fischermi@t-online.de \
--to=fischermi@t-online.de \
--cc=gdb-patches@sourceware.org \
/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