From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [2/2] RFC: build machoread.c in more cases
Date: Wed, 02 Jan 2013 14:54:00 -0000 [thread overview]
Message-ID: <87y5gb7i03.fsf@fleche.redhat.com> (raw)
In-Reply-To: <87fw394tl1.fsf@fleche.redhat.com> (Tom Tromey's message of "Thu, 13 Dec 2012 12:53:30 -0700")
>>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
Tom> I noticed that machoread.c is only built for Darwin.
Tom> This seems wrong to me. It seems like it should instead be built
Tom> whenever the needed BFD code is built. This is what we do for
Tom> elfread.c.
I'm checking this in now.
Tom
prev parent reply other threads:[~2013-01-02 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 19:53 Tom Tromey
2012-12-13 20:03 ` Pedro Alves
2013-01-02 14:54 ` Tom Tromey [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=87y5gb7i03.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@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