From: Andreas Schwab <schwab@suse.de>
To: gdb@sourceware.org
Cc: Tom Tromey <tromey@redhat.com>
Subject: Re: Automatic dependency tracking
Date: Wed, 25 Jun 2008 19:30:00 -0000 [thread overview]
Message-ID: <je3an19uud.fsf@sykes.suse.de> (raw)
In-Reply-To: <20080625182858.GA25575@caradoc.them.org> (Daniel Jacobowitz's message of "Wed, 25 Jun 2008 14:28:58 -0400")
Daniel Jacobowitz <drow@false.org> writes:
> Option four: We could borrow logic from BFD to generate dependency
> lists. What's going on with this code anyway? Why does BFD need
> dependency lists in Makefile.am if it uses automake?
It's a side effect of using the cygnus option.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2008-06-25 19:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200806152203.14626.pedro@codesourcery.com>
[not found] ` <u3anel69s.fsf@gnu.org>
[not found] ` <20080616012617.GA8944@caradoc.them.org>
[not found] ` <g35201$2uf$2@ger.gmane.org>
[not found] ` <m33an413yx.fsf@fleche.redhat.com>
2008-06-25 18:29 ` Daniel Jacobowitz
2008-06-25 19:30 ` Andreas Schwab [this message]
2008-06-25 21:35 ` Stan Shebs
2008-06-26 0:08 ` Tom Tromey
2008-06-26 1:47 ` Joel Brobecker
2008-06-26 9:48 ` Andrew STUBBS
2008-06-26 17:30 ` Tom Tromey
2008-06-27 10:23 ` Andrew STUBBS
2008-06-27 14:03 ` Daniel Jacobowitz
2008-06-27 16:09 ` Andrew STUBBS
2008-06-27 14:30 ` Tom Tromey
2008-06-28 19:20 ` Mark Kettenis
2008-06-28 19:31 ` Tom Tromey
2008-06-29 14:47 ` Daniel Jacobowitz
2008-06-29 15:36 ` Tom Tromey
2008-06-29 16:26 ` Tom Tromey
2008-06-29 14:42 ` 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=je3an19uud.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=gdb@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