Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: Finding source files under cygwin
Date: Fri, 13 Sep 2002 21:40:00 -0000	[thread overview]
Message-ID: <20020914044042.GC23240@redhat.com> (raw)
In-Reply-To: <3D82897C.81376AD6@agilent.com>

[NOTE: Reply-To set to gdb-patches]

On Fri, Sep 13, 2002 at 05:57:32PM -0700, Earl Chew wrote:
>One fix I can think of is to fix open_source_file() using
>#ifdef __CYGWIN__ to silently subsitute /cygdrive/d/xxx/yyy/zzz
>instead.
>
>A variation on this is to make the fix in buildsym.c instead
>(ie store the corrected version of the directory instead of
>patching it later). I don't think this is the best way to go.
>
>Another fix is to make source.c use ; (semicolon) as a path
>separator instead of : (colon) should HAVE_DOS_BASED_FILE_SYSTEM
>be true. The downside here is that it might be surprising
>to current cygwin users.

This one is out.  This would break backwards compatibility and would be
incompatible with the convention used in the rest of cygwin.

The simplest solution is to just compile your object files using
the /cygdrive/d/xxx/yyy/zzz syntax.  The ability to use this syntax
is one of the motivations for cygwin.

However, if you want to provide a patch for either open_source_file
or buildsym.c, I'll gladly review it.

cgf


  reply	other threads:[~2002-09-14  4:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-13 17:57 Finding source files under Cygwin Earl Chew
2002-09-13 21:40 ` Christopher Faylor [this message]
2002-09-16 12:07 ` Earl Chew
2002-09-16 12:48   ` Finding source files under cygwin Christopher Faylor
2002-09-16 13:14   ` Finding source files under Cygwin Earl Chew
2002-09-16 13:37   ` [RFC PATCH] Finding files in source trees (was Re: Finding source files under Cygwin) Earl Chew
2002-09-16 15:02     ` Daniel Jacobowitz
2002-09-16 15:17       ` Earl Chew

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=20020914044042.GC23240@redhat.com \
    --to=cgf@redhat.com \
    --cc=gdb-patches@sources.redhat.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