From: Richard Earnshaw <rearnsha@gcc.gnu.org>
To: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: ARM Simulator build broken
Date: Wed, 17 Nov 2004 15:04:00 -0000 [thread overview]
Message-ID: <1100703804.22014.42.camel@pc960.cambridge.arm.com> (raw)
In-Reply-To: <200411161535.iAGFZUN2014411@ignucius.se.axis.com>
On Tue, 2004-11-16 at 15:35, Hans-Peter Nilsson wrote:
> > From: Richard Earnshaw <rearnsha@gcc.gnu.org>
> > Cc: gdb-patches@sources.redhat.com
>
> > Here's my proposed patch:
> >
> > <date> Richard Earnshaw <rearnsha@arm.com>
> >
> > * Make-common.in (sim_basics_headers): New.
> > (sim_main_headers): Move basics headers and sub-dependencies
> > to sim_basics_headers). Add the dependencies through that.
> > (sim-load.c): Depend on sim_basics_headers not
> > sim_main_headers.
> >
> > OK?
>
> I was preparing almost the same patch, just naming the macro
> sim_basics_h_headers!
>
> BTW, you shouldn't have edited out sim-arange.c, a gcc -MM says
> it's actually included from sim-basics.h (and from looking at
> the code). For the same reason sim-assert.h should be in
> sim_basics_headers. Maybe all files should use the
> $(sim-assert_h) et al macros.
The list of headers I used was the list directly in sim-basics.h. I
only moved existing includes from sim_main_headers and then added
further ones at the first level that were obviously missing. So if it's
wrong now it was wrong before.
The best way to do all this is to define a series of macros
sim-basics_h, sim-assert-h etc, and for each of these to list the macros
that form the direct dependencies.
But that's a fair bit of work... :-( ... and it needs active
maintenance to keep it up to date.
R.
next prev parent reply other threads:[~2004-11-17 15:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 12:40 Richard Earnshaw
2004-11-16 15:24 ` Richard Earnshaw
2004-11-16 15:36 ` Hans-Peter Nilsson
2004-11-17 15:04 ` Richard Earnshaw [this message]
2004-11-17 16:06 ` Richard Earnshaw
2004-11-17 18:25 ` Hans-Peter Nilsson
2004-11-17 20:38 ` Andrew Cagney
2004-11-18 0:08 ` Hans-Peter Nilsson
2004-11-18 10:22 ` Richard Earnshaw
2004-11-24 18:42 ` Alexandre Oliva
2004-11-25 10:31 ` Richard Earnshaw
2004-11-25 10:48 ` Richard Earnshaw
2004-11-29 18:27 ` Alexandre Oliva
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=1100703804.22014.42.camel@pc960.cambridge.arm.com \
--to=rearnsha@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=hans-peter.nilsson@axis.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