Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Richard Hirst <rhirst@linuxcare.com>
To: Randolph Chung <randolph@tausq.org>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Proposed change to arch/parisc/Makefile and generation of offset.h
Date: Sat, 2 Feb 2002 14:07:41 +0000	[thread overview]
Message-ID: <20020202140740.GD2884@sleepie.demon.co.uk> (raw)
In-Reply-To: <20020202063408.GA604@tausq.org>

On Fri, Feb 01, 2002 at 10:34:08PM -0800, Randolph Chung wrote:
> I'd like to check this change in to change how we clean up and
> regenerate include/asm-parisc/offset.h. This will let us ship a working
> offset.h in our kernel-headers package to be used by glibc builds, and
> will also allow things like gdb to build.
> 
> (basically, the problem right now is that offset.h is removed after a
> 'make clean')
> 
> With this change, 'make dep' will regenerate the offset.h and allow the
> kernel dependency mechanism to kick in. 'make mrproper' will remove the
> offset.h file, but 'make clean' will not.
> 
> comments?

Sounds like a reasonable compromise to me.  Only snag is that if you
build a 32 bit kernel, make clean, change config for a 64 bit kernel,
then make again, you will build a 64 bit kernel with the wrong offset.h.

Would be nice if 'make' could verify that the offset.h ifile was correct,
without changing it (and so triggering dependencies).  If it could do
that, it could regenerate it only if it was wrong.

Richard

  reply	other threads:[~2002-02-02 14:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-02  6:34 [parisc-linux] Proposed change to arch/parisc/Makefile and generation of offset.h Randolph Chung
2002-02-02 14:07 ` Richard Hirst [this message]
2002-02-02 16:44   ` Randolph Chung
2002-02-02 16:42     ` Richard Hirst

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=20020202140740.GD2884@sleepie.demon.co.uk \
    --to=rhirst@linuxcare.com \
    --cc=parisc-linux@parisc-linux.org \
    --cc=randolph@tausq.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