From: Ian Lance Taylor <iant@google.com>
To: Dave Korn <dave.korn.cygwin@googlemail.com>
Cc: Tom Tromey <tromey@redhat.com>,
Binutils Development <binutils@sourceware.org>,
gdb-patches@sourceware.org
Subject: Re: RFA: dwarf2.h merge
Date: Sat, 11 Jul 2009 08:25:00 -0000 [thread overview]
Message-ID: <m3ocrs2gkl.fsf@google.com> (raw)
In-Reply-To: <4A57B161.8090806@gmail.com> (Dave Korn's message of "Fri\, 10 Jul 2009 22\:23\:45 +0100")
Dave Korn <dave.korn.cygwin@googlemail.com> writes:
> Alan Modra wrote:
>> On Fri, Jul 10, 2009 at 08:55:23AM -0600, Tom Tromey wrote:
>>> * Makefile.am (dwarf2.lo): Use dwarf2.h, not elf/dwarf2.h.
>>> (elf-eh-frame.lo): Likewise.
>>> (elf32-bfin.lo): Likewise.
>>> (elf32-frv.lo): Likewise.
>>> (elf32-xc16x.lo): Likewise.
>>
>> You did this by hand? "make dep-am" in bfd, opcodes, binutils, gas,
>> gprof, ld! Oh well, binutils parts OK anyway.
>>
>
> Side issue: What's the difference between "make dep" and "make dep-am"?
"make dep" changes Makefile in your build directory. "make dep-am"
changes Makefile.am in your source directory. For that matter, we still
have "make dep-in" which changes Makefile.in in your source directory.
Basically "make dep" and "make dep-in" could conceivably be useful if
you can't figure out how to run automake. In practice I don't think
anybody would notice if we got rid of them.
Ian
prev parent reply other threads:[~2009-07-11 0:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 15:15 Tom Tromey
2009-07-10 17:16 ` Alan Modra
2009-07-10 17:22 ` Tom Tromey
2009-07-11 8:36 ` Ralf Wildenhues
2009-07-11 0:45 ` Dave Korn
2009-07-11 8:25 ` Ian Lance Taylor [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=m3ocrs2gkl.fsf@google.com \
--to=iant@google.com \
--cc=binutils@sourceware.org \
--cc=dave.korn.cygwin@googlemail.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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