From: Ian Lance Taylor <iant@google.com>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Cc: binutils@sourceware.org
Subject: Re: dependency tracking in ld
Date: Mon, 17 Aug 2009 17:59:00 -0000 [thread overview]
Message-ID: <m3d46uifai.fsf@google.com> (raw)
In-Reply-To: <20090815124327.GB20656@gmx.de> (Ralf Wildenhues's message of "Sat\, 15 Aug 2009 14\:43\:28 +0200")
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.
Ian
next prev parent reply other threads:[~2009-08-17 16:19 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 [this message]
2009-08-18 19:02 ` Ralf Wildenhues
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 binutils Ralf Wildenhues
2009-08-18 7:50 ` Nick Clifton
2009-08-15 12:45 ` dependency tracking in bfd Ralf Wildenhues
2009-08-18 7:48 ` 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
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 opcodes Ralf Wildenhues
2009-08-18 14:18 ` 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=m3d46uifai.fsf@google.com \
--to=iant@google.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=binutils@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).