From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Cc: Iain Sandoe <developer@sandoe-acoustics.co.uk>,
Tristan Gingold <gingold@adacore.com>
Subject: Re: [Patch Darwin] head build fixes for i686-darwin9/x86_64-darwin10.
Date: Mon, 24 Dec 2012 03:56:00 -0000 [thread overview]
Message-ID: <201212232256.26065.vapier@gentoo.org> (raw)
In-Reply-To: <59ABFF71-CA26-452C-B9B2-9B0FC6AAE2BD@sandoe-acoustics.co.uk>
[-- Attachment #1: Type: Text/Plain, Size: 1068 bytes --]
On Thursday 29 December 2011 15:30:31 Iain Sandoe wrote:
> 1/ a "maybe used un-initialized" (in machoread.c)
looks like this has been fixed since:
commit 9ba6fb7f0b383d2f19536d8224fe4e692bd30e2d
Author: Tristan Gingold <gingold@adacore.com>
Date: Thu Feb 16 14:57:01 2012 +0000
2012-02-16 Josh Matthews <josh@joshmatthews.net>
* machoread.c: Initialize nbr_syms to avoid warnings-as-errors failure.
> 2/ DR_FIRSTADDR and cousins are undefined.
> (the fragment below is copied verbatim from gdb-7.3.1 - is there some
> reason to expect that it should have been defined elsewhere?)
looks like this has been fixed since:
commit 39e980b3953f98e66359aabc733c3d9dd4785b82
Author: Joel Brobecker <brobecker@gnat.com>
Date: Wed Feb 1 10:54:06 2012 +0000
Fix build error in Darwin port.
gdb/ChangeLog:
From: Josh Matthews <josh@joshmatthews.net> (tiny change)
Fix build error in Darwin port.
* i386-darwin-nat.c: Include i386-nat.h.
> 3/ (Darwin 9 only)
> TASK_DYLD_INFO_COUNT etc. are not defined.
which leaves this one uncommitted. i'll follow up.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-12-24 3:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 20:32 Iain Sandoe
2012-01-02 11:40 ` Pedro Alves
2012-01-02 14:39 ` Tristan Gingold
2012-12-24 3:57 ` Mike Frysinger
2012-12-24 4:27 ` Joel Brobecker
2012-12-24 5:09 ` Mike Frysinger
2012-12-24 3:56 ` Mike Frysinger [this message]
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=201212232256.26065.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=developer@sandoe-acoustics.co.uk \
--cc=gdb-patches@sourceware.org \
--cc=gingold@adacore.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