From: Jonas Maebe <jonas.maebe@elis.ugent.be>
To: archer@sourceware.org
Subject: Re: Fixes for Mac OS X/x86 building/running
Date: Thu, 12 Mar 2009 19:28:00 -0000 [thread overview]
Message-ID: <CF5E7621-4572-4D9A-86C3-DE0FD47D27EA@elis.ugent.be> (raw)
In-Reply-To: <20090312184042.GE8386@adacore.com>
On 12 Mar 2009, at 19:40, Joel Brobecker wrote:
>> Less cursory testing shows that it doesn't work fine. The problem is
>> that[...]
>
> I recommend that you discuss this issue on gdb@ rather than the Archer
> list, because the port originates from GDB, not Archer:
I checked my GDB cvs checkout and could not find any trace of gdb/
machoread.c nor of gdb/darwin-nat.c. That's why I thought it was
Archer-specific. But now I do see that it's mentioned in the Changelog
file. Apparently, because I started my cvs checkout from a tbz source
snapshot, I had some kind of sticky tag. I've now done a "cvs up -A",
and now I have the file. Sorry for the trouble.
> I think you have
> more chances of reaching some developers that know a little more about
> MacOS. The author of the MacOS port is Tristan Gingold, and I'm not
> sure
> he's either on gdb@ or archer@, so I'd recommend CC'ing him in your
> report (gingold /AT/ adacore.com).
Thanks, I'll keep that in mind.
> The reviewer was Stan Shebs, who used
> to work at Apple...
Yes, I remember him. He used to their main GCC guy, if I remember
correctly (or at least the most vocal one :)
> PS: I'll take a look at your first patch in a moment, and I expect to
> be able to approve it for inclusion in the FSF tree.
Thanks!
Jonas
next prev parent reply other threads:[~2009-03-12 19:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 19:41 Jonas Maebe
2009-03-12 18:30 ` Jonas Maebe
2009-03-12 18:41 ` Joel Brobecker
2009-03-12 19:28 ` Jonas Maebe [this message]
2009-03-12 20:56 ` Tom Tromey
2009-03-12 21:45 ` Jonas Maebe
2009-03-12 22:19 ` [Archer] " Joel Brobecker
2009-03-12 22:33 ` Tom Tromey
2009-03-12 23:07 ` Jonas Maebe
2009-03-12 23:25 ` Tom Tromey
2009-03-12 22:40 ` 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=CF5E7621-4572-4D9A-86C3-DE0FD47D27EA@elis.ugent.be \
--to=jonas.maebe@elis.ugent.be \
--cc=archer@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).