mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Jan Beulich <JBeulich@novell.com>
Cc: Andreas Gruenbacher <agruen@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [patch] kbuild: building with a mostly-clean /usr/src/linux and O=
Date: Sat, 10 Sep 2005 08:33:52 +0200	[thread overview]
Message-ID: <20050910063352.GA17177@mars.ravnborg.org> (raw)
In-Reply-To: <431EB0AF02000078000241C0@emea1-mh.id2.novell.com>

On Wed, Sep 07, 2005 at 09:19:43AM +0200, Jan Beulich wrote:
> Unfortunately this isn't sufficient, yet. In the architecture-specific
> makefiles asm-offsets.s (or however the specific architectures call
> this) now need their dependencies on include/linux/version.h changed (I
> wonder whether it wouldn't be more efficient to centralize these
> dependencies into an architecture-independent file, perhaps at once
> applying consistent naming across all architectures)

This topic has been on my mind to implment over a long time.
So I took a stamp on it and it hit -linus this night.

Dependencies on arch/$(ARCH)/kernel/asm-offsets.s is now tracked
like any other dependency - so we now at last have full dependency
checks for asm-offsets.h.
Take a look at the Kbuild file in the top-level directory.

With respect to the patch posted below I recall I had to zap
two $(objtree) to fix alpha build.
Patch by Jan Dittmer - see 946dc121d7d1c606f6bbeb8ae778963a1e2ff59c

But that may have changed now after introducing generic asm-offsets.h
support.

	Sam

      reply	other threads:[~2005-09-10  6:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-06 20:13 Andreas Gruenbacher
2005-09-06 20:25 ` Sam Ravnborg
2005-09-07  1:03   ` Andreas Gruenbacher
2005-09-07  7:19     ` Jan Beulich
2005-09-10  6:33       ` Sam Ravnborg [this message]

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=20050910063352.GA17177@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=JBeulich@novell.com \
    --cc=agruen@suse.de \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®