From: "Michael Fischer" <fischermi@t-online.de>
To: <gdb-patches@sourceware.org>
Subject: AW: AW: [PATCH] source.s: Fix problem handling windows like path with MinGW
Date: Sun, 18 Jun 2006 09:03:00 -0000 [thread overview]
Message-ID: <JLEAKDMELBINENLADICFAEFKCIAA.fischermi@t-online.de> (raw)
In-Reply-To: <735259CC-31B1-4B61-A586-AF0B642CA374@monami-software.com>
I have make a quick test and added:
#undef DIRNAME_SEPARATOR
#define DIRNAME_SEPARATOR ';'
after all includes in source.c
This is working now!
I think we should change defs.h from:
#ifdef __MSDOS__
# define CANT_FORK
# define GLOBAL_CURDIR
# define DIRNAME_SEPARATOR ';'
#endif
#ifndef DIRNAME_SEPARATOR
#define DIRNAME_SEPARATOR ':'
#endif
to:
#ifdef __MSDOS__
#define CANT_FORK
#define GLOBAL_CURDIR
#endif
#if defined(__MSDOS__) || defined(_WIN32) || defined(__OS2__) || defined
(__CYGWIN__)
#define DIRNAME_SEPARATOR ';'
#endif
#ifndef DIRNAME_SEPARATOR
#define DIRNAME_SEPARATOR ':'
#endif
But I do not know if this will breaks the other one.
I saw this define construct will be used in filenames to.
Michael
-----Ursprungliche Nachricht-----
Von: gdb-patches-owner@sourceware.org
[mailto:gdb-patches-owner@sourceware.org]Im Auftrag von Masaki Muranaka
Gesendet: Sonntag, 18. Juni 2006 06:57
An: Eli Zaretskii
Cc: Michael Fischer; gdb-patches@sourceware.org
Betreff: Re: AW: [PATCH] source.s: Fix problem handling windows like
path with MinGW
On 2006/06/18, at 12:23, Eli Zaretskii wrote:
> [Please don't take this discussion off the mailing list.]
>
>> From: "Michael Fischer" <fischermi@t-online.de>
>> Date: Sat, 17 Jun 2006 23:32:25 +0200
>>
>> Why ":" and not ";" ?
>>
>> If I compile the GDB under MinGW, DIRNAME_SEPARATOR was set to ":".
>> If you take a look in gdb\defs.h, ";" is only defined in case of
>> __MSDOS__. I think MinGW will not set this define?!
>
> What happens if you modify defs.h to define DIRNAME_SEPARATOR as `;'?
> Does the problem go away?
>
>> I think in this case, we should change the add_path function too.
>
> I think if DIRNAME_SEPARATOR is `;', add_path will do what you need.
>
> Could you please check that?
BTW, Why do we use DIRNAME_SEPARATOR, instead of PATH_SEPARATOR ?
As PATH_SEPARATOR is detected by configure, it is trustable.
I think they will be same value on self builds, right?
Also we can choice to modify xm-.h on cross builds.
--
Masaki Muranaka
Monami software
next prev parent reply other threads:[~2006-06-18 9:03 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 ` Michael Fischer [this message]
2006-06-18 19:47 ` AW: " Eli Zaretskii
2006-06-18 20:05 ` AW: " Michael Fischer
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=JLEAKDMELBINENLADICFAEFKCIAA.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