public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] offsets.h generation
Date: Mon, 19 May 2003 17:13:21 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723705946@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705941@msgid-missing>

On Mon, May 19, 2003 at 02:30:57PM +1000, Peter Chubb wrote:
Content-Description: message body text
> 
> At present, if you change something that means offsets.h should be
> regenerated, the automatic dependencies mechanism doesn't do it.
> 
> Herewith a patch that adds proper dependency generation for 
>  printoffsets.s (and hence offsets.h)

I agree with the intention, but not the solution.
Other architectures generate a .s file from a .c file, and
filechk_gen-asm-offsets in the top-level Makefile is used to retreive
the asm offset parameters.

In this way you use the kbuild mecanishm to find dependencies,
and ia64 shift to do it the same way as other architectures.
See i386, sparc and other for a template how to do it.
Note that most of the architectures list too much dependencies
in the arch specific makefile. I will clean that up sometime.

Would you mind trying to look into this solution?

	Sam


  reply	other threads:[~2003-05-19 17:13 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 [this message]
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
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-105590723705946@msgid-missing \
    --to=sam@ravnborg.org \
    --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