From: Masaki Muranaka <monaka@monami-software.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: fischermi@t-online.de, gdb-patches@sourceware.org
Subject: Re: AW: [PATCH] source.s: Fix problem handling windows like path with MinGW
Date: Mon, 19 Jun 2006 00:27:00 -0000 [thread overview]
Message-ID: <245F9D05-6921-4988-9422-C0444CD688E6@monami-software.com> (raw)
In-Reply-To: <uodwq2qs0.fsf@gnu.org>
On 2006/06/19, at 4:43, Eli Zaretskii wrote:
>> Cc: "Michael Fischer" <fischermi@t-online.de>,
>> gdb-patches@sourceware.org
>> From: Masaki Muranaka <monaka@monami-software.com>
>> Date: Sun, 18 Jun 2006 13:56:32 +0900
>>
>> BTW, Why do we use DIRNAME_SEPARATOR, instead of PATH_SEPARATOR ?
>> As PATH_SEPARATOR is detected by configure, it is trustable.
>
> Not really: MinGW lacks a port of Bash, so people are using all kinds
> of replacements, which may well produce `:' as PATH_SEPARATOR. In
> particular, two popular ports, the ones from Cygwin and MSYS, will do
> that, I think.
>
> Cross builds are another such case.
>
> So I think we should simply hard-code that in Windows native ports.
GCC3.4.x uses PATH_SEPARATOR and it seems that has
no issue. What is the difference between GCC and GDB?
--
Masaki Muranaka
Monami software
next prev parent reply other threads:[~2006-06-19 0:27 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 ` 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 [this message]
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=245F9D05-6921-4988-9422-C0444CD688E6@monami-software.com \
--to=monaka@monami-software.com \
--cc=eliz@gnu.org \
--cc=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