From: Peter Chubb <peter@chubb.wattle.id.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] offsets.h generation
Date: Tue, 20 May 2003 09:15:43 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705958@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705941@msgid-missing>
>>>>> "David" = David Mosberger <davidm@napali.hpl.hp.com> writes:
>>>>> On Tue, 20 May 2003 11:26:31 +1000, Peter Chubb <peter@chubb.wattle.id.au> said:
Peter> OK, here's a patch that does it that way. Because some of the
Peter> needed header files in turn depend on a symbol from offsets.h,
Peter> I had to create a dummy one `by hand' if it didn't previously
Peter> exist. A timestamp file, include/asm-ia64/.offsets.h.stamp,
Peter> tracks when this was done so that 'make' after 'make clean'
Peter> works; and 'make' after 'make' works.
David> Is processor.h the only cause of this recursive dependency? As
David> far as I remember, we don't even need to include offsets.h in
David> processor.h anymore. It used to be necessary for get_wchan(),
David> but that's now an out-of-line function.
I'll try deleting that one tomorrow when I'm in at work... if we can
get rid of it, everything becomes *much* cleaner.
Peter C
next prev parent reply other threads:[~2003-05-20 9:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 4:30 [Linux-ia64] offsets.h generation Peter Chubb
2003-05-19 17:13 ` Sam Ravnborg
2003-05-20 1:26 ` Peter Chubb
2003-05-20 4:40 ` Sam Ravnborg
2003-05-20 6:31 ` David Mosberger
2003-05-20 9:15 ` Peter Chubb [this message]
2003-05-23 1:09 ` Peter Chubb
2003-05-23 1:50 ` David Mosberger
2003-05-26 23:25 ` Peter Chubb
2003-05-27 0:03 ` Peter Chubb
2003-05-27 0:03 ` Peter Chubb
2003-05-31 0:34 ` David Mosberger
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=marc-linux-ia64-105590723705958@msgid-missing \
--to=peter@chubb.wattle.id.au \
--cc=linux-ia64@vger.kernel.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