Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Danny Backx <danny.backx@scarlet.be>
To: gdb-patches <gdb-patches@sourceware.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
	Joel Brobecker <brobecker@adacore.com>,
	        Pedro Alves <pedro@codesourcery.com>,
	        Daniel Jacobowitz <drow@false.org>
Subject: Re: shared lib dos filename style - one more question
Date: Wed, 14 Oct 2009 20:18:00 -0000	[thread overview]
Message-ID: <1255551583.10921.271.camel@pavilion> (raw)
In-Reply-To: <20091012204451.GA17607@caradoc.them.org>

On Tue, 2009-10-13 at 20:25 +0200, Eli Zaretskii wrote:
> > >  /sysroot/c:/path/to/a
> > >  /sysroot/d:/path/to/b
> > 
> > Good point. Either form works for me.
> 
> I vote for the second, because it covers the case that the colon is
> part of a real Unix file name.

Ok so I guess the table becomes :

> 1.  /path/to/a -> /path/to/a
> 2.  \path/to/a -> /path/to/a
> 3.  \path\to\a -> /path/to/a
> 4.  c: -> c:
> 5.  c:\path\to\a -> c:/path/to/a

so the only thing that happens is backslash to forward slash
translation.

Right ?

On Mon, 2009-10-12 at 16:44 -0400, Daniel Jacobowitz wrote:
> Anyway, I'd prefer a global solution rather than one local to
> solib_find.  For instance, we've had trouble with FILENAME_CMP
> depending on which host the program was *compiled* on.

Do you mean that the call to unixify() should happen in openp() instead
of in solib_find() ? There's also a call to open() so I guess this
should be changed as well.

	Danny
-- 
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info


  parent reply	other threads:[~2009-10-14 20:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-26 13:49 Danny Backx
2009-10-07 20:05 ` Danny Backx
2009-10-07 20:11   ` Daniel Jacobowitz
2009-10-08 16:01     ` Danny Backx
2009-10-09 17:36       ` Joel Brobecker
2009-10-09 18:58         ` Danny Backx
2009-10-10  2:19           ` Joel Brobecker
2009-10-12 20:05             ` Danny Backx
2009-10-12 20:28               ` Eli Zaretskii
2009-10-13  5:24                 ` Joel Brobecker
2009-10-13 10:57                   ` Pedro Alves
2009-10-13 15:30                     ` Joel Brobecker
2009-10-13 18:23                       ` Eli Zaretskii
2009-10-13 18:12                   ` Eli Zaretskii
2009-10-13 18:19                     ` Daniel Jacobowitz
2009-10-12 20:45             ` Daniel Jacobowitz
2009-10-13  5:21               ` Joel Brobecker
2009-10-13 15:51                 ` Daniel Jacobowitz
2009-10-14 20:18               ` Danny Backx [this message]
2009-10-17  4:16                 ` Joel Brobecker

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=1255551583.10921.271.camel@pavilion \
    --to=danny.backx@scarlet.be \
    --cc=brobecker@adacore.com \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    /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