public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: Ian Lance Taylor <iant@google.com>
Cc: binutils@sourceware.org
Subject: Re: dependency tracking in ld
Date: Tue, 18 Aug 2009 19:02:00 -0000	[thread overview]
Message-ID: <20090818184815.GF30742@gmx.de> (raw)
In-Reply-To: <m3d46uifai.fsf@google.com>

* Ian Lance Taylor wrote on Mon, Aug 17, 2009 at 06:19:33PM CEST:
> Ralf Wildenhues <Ralf.Wildenhues@gmx.de> writes:
> 
> > The removal of the cygnus Automake option requires a few changes in the
> > code.  I hope I got all relevant ones right.  The dependency tracking
> > should be tracking all files that have been tracked before, too.
> > However, there are still all the e*.o files which do not have dep
> > tracking yet.  If you want this, then please say so, because it's a
> > matter of adding something like this line:
> >   EXTRA_ld_new_SOURCES += $(ALL_EMULATIONS:.o=.c) $(ALL_64_EMULATIONS:.o=.c)
> 
> I think that depencency tracking for the ld/emultempl/*.em would be
> appropriate.  They include a bunch of ld .h files.

OK good.  I have tested that combination, too.

Of the patch series in this email thread, only this patch you have
replied to (plus the above quoted EXTRA_ld_new_SOURCES line):
<http://thread.gmane.org/gmane.comp.gnu.binutils/42956/focus=42957>
still need approval.

Thanks everyone for all the reviews so far!

Cheers,
Ralf

  reply	other threads:[~2009-08-18 18:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-15 12:42 dependency tracking in ld bfd binutils gas gprof opcodes Ralf Wildenhues
2009-08-15 12:43 ` dependency tracking in ld Ralf Wildenhues
2009-08-17 17:59   ` Ian Lance Taylor
2009-08-18 19:02     ` Ralf Wildenhues [this message]
2009-08-19  2:38       ` Alan Modra
2009-08-19  6:44         ` One issue with ld He Yunlong-B20256
2009-08-28  8:18           ` Alan Modra
2009-08-28  8:23             ` Alan Modra
2009-08-28  9:58               ` He Yunlong-B20256
2009-08-28 10:57                 ` Alan Modra
2009-08-15 12:45 ` dependency tracking in bfd Ralf Wildenhues
2009-08-18  7:48   ` Nick Clifton
2009-08-15 12:45 ` dependency tracking in binutils Ralf Wildenhues
2009-08-18  7:50   ` Nick Clifton
2009-08-15 12:46 ` dependency tracking in opcodes Ralf Wildenhues
2009-08-18 14:18   ` Nick Clifton
2009-08-15 12:46 ` dependency tracking in gprof Ralf Wildenhues
2009-08-18  7:51   ` Nick Clifton
2009-08-15 12:46 ` dependency tracking in gas Ralf Wildenhues
2009-08-16  8:40   ` Ralf Wildenhues
2009-08-18 10:54   ` Nick Clifton

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=20090818184815.GF30742@gmx.de \
    --to=ralf.wildenhues@gmx.de \
    --cc=binutils@sourceware.org \
    --cc=iant@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).