From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: dave.korn@artimi.com, gdb-patches@sources.redhat.com, me@cgf.cx
Subject: Re: [PATCH] Your patch from 20050512 b0rked on cygwin!
Date: Sun, 18 Sep 2005 01:23:00 -0000 [thread overview]
Message-ID: <20050918012330.GQ8777@nevyn.them.org> (raw)
In-Reply-To: <200508171907.j7HJ7Gq8024834@elgar.sibelius.xs4all.nl>
Dave, is Cygwin really still broken? I never saw a followup to this.
On Wed, Aug 17, 2005 at 09:07:16PM +0200, Mark Kettenis wrote:
> > From: "Dave Korn" <dave.korn@artimi.com>
> > Date: Wed, 17 Aug 2005 17:39:05 +0100
> >
> > [Please keep me in the Cc: line, as I don't subscribe to gdb-patches]
> >
> > Hi Mark,
> >
> > Your patch to unconditionally include shared library code:
> >
> > Original patch -
> > http://sources.redhat.com/ml/gdb-patches/2005-05/msg00043.html
> > Respin that went in -
> > http://sources.redhat.com/ml/gdb-patches/2005-05/msg00198.html
> >
> > ... appears to have borked cygwin. No criticism of yourself should be read
> > into this fact: you did appeal for cygwin testing, and nobody stepped up to
> > the plate, so I'm as much to mea culpa as anybody.
>
> Sorry 'bout that.
[snip; see the archives]
> > So I would appreciate a bit of review (and preferably from someone who
> > knows better than me what's going on in this corner of the world!).
>
> Ideally, the cygwin shared library code would be converted to use the
> solib.c mechanism. However, that's a bit more work, so I can image
> we'd want this "quick" fix in first. But Chris Faylor is the
> maintainer of this code, so you'll need his approval.
Copying Chris, in case he didn't see the original.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-09-18 1:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-17 17:59 Dave Korn
2005-08-17 19:25 ` Mark Kettenis
2005-09-18 1:23 ` Daniel Jacobowitz [this message]
2005-09-18 1:31 ` Christopher Faylor
2005-09-18 1:34 ` 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=20050918012330.GQ8777@nevyn.them.org \
--to=drow@false.org \
--cc=dave.korn@artimi.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
--cc=me@cgf.cx \
/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