From: Alistair John Strachan <alistair@devzero.co.uk>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.28-rc1
Date: Fri, 24 Oct 2008 13:52:45 +0100 [thread overview]
Message-ID: <200810241352.45745.alistair@devzero.co.uk> (raw)
In-Reply-To: <200810241345.04966.rjw@sisk.pl>
On Friday 24 October 2008 12:45:04 Rafael J. Wysocki wrote:
> On Friday, 24 of October 2008, Alistair John Strachan wrote:
> > On Friday 24 October 2008 05:10:29 Linus Torvalds wrote:
> > > It's been two weeks, so it's time to close the merge window. A
> > > 2.6.28-rc1 is out there, and it's hopefully all good.
> >
> > It seems if you have a broken asm/ symlink in include/ (which happened as
> > a result of the x86 header moves, for me) the kernel won't try to update
> > it appropriately, and this breaks "make prepare".
> >
> > $ make ARCH=x86_64 prepare
> > CHK include/linux/version.h
> > CHK include/linux/utsrelease.h
> > GEN include/asm/asm-offsets.h
> > /bin/sh: include/asm/asm-offsets.h: No such file or directory
> > make[1]: *** [include/asm/asm-offsets.h] Error 1
> > make: *** [prepare0] Error 2
> >
> > rm -f include/asm fixes it
> >
> > This was just from taking a 2.6.27 tree, git clean -d -f, git pull, make
> > oldconfig. Might be a nice thing to fix?
>
> Hm, I didn't have any problems with compiling .28-rc1 on x86_64.
>
> [Confused.]
This should reproduce it (whether or not it's a use-case we care about is
another matter). First, make sure your include/asm symlink has been removed,
then execute the following sequence:
git reset --hard v2.6.27 ; git clean -d -f
git status ("Nothing to commit")
cp /path/to/config .config
make oldconfig prepare
git clean -d -f ; git reset --hard
git status ("Nothing to commit")
Observe at this point that include/asm is valid and points to include/asm-x86,
despite the clean and reset (I guess this file is being ignored). Now:
git reset --hard v2.6.28-rc1 (Or whatever other method you might choose)
git clean -d -f (Removes include/asm-x86)
Observe at this point that include/asm is now invalid, and still points to the
removed include/asm-x86 directory.
cp /path/to/config .config
make oldconfig prepare
Should fail at this point:
scripts/kconfig/conf -o arch/x86/Kconfig
#
# configuration written to .config
#
scripts/kconfig/conf -s arch/x86/Kconfig
CHK include/linux/version.h
UPD include/linux/version.h
CHK include/linux/utsrelease.h
UPD include/linux/utsrelease.h
CC kernel/bounds.s
GEN include/linux/bounds.h
CC arch/x86/kernel/asm-offsets.s
GEN include/asm/asm-offsets.h
/bin/sh: include/asm/asm-offsets.h: No such file or directory
make[2]: *** [include/asm/asm-offsets.h] Error 1
make[1]: *** [prepare0] Error 2
make: *** [prepare] Error 2
Can you confirm?
I checked out Makefile and I believe it occurs because the current checks only
make sure a symlink exists, and if it does exist that its target matches up
with the selected architecture. It doesn't actually check the destination of
the symlink is valid.
I'd suggest that it should do that too, and if the destination doesn't exist,
re-write the symlink when it does "mkdir include/asm-x86" further down, but
I'm not a kbuild expert.
--
Cheers,
Alistair.
next prev parent reply other threads:[~2008-10-24 12:53 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 4:10 Linux 2.6.28-rc1 Linus Torvalds
2008-10-24 4:14 ` Roland Dreier
2008-10-24 18:08 ` Greg KH
2008-10-24 11:24 ` Alistair John Strachan
2008-10-24 11:45 ` Rafael J. Wysocki
2008-10-24 12:52 ` Alistair John Strachan [this message]
2008-10-24 13:13 ` Alexey Dobriyan
2008-10-24 14:56 ` git-clean [Was: Linux 2.6.28-rc1] Björn Steinbrink
2008-10-24 15:17 ` Linux 2.6.28-rc1 Linus Torvalds
2008-10-24 19:22 ` Sam Ravnborg
2008-10-24 22:31 ` David Miller
2008-10-24 22:51 ` Sam Ravnborg
2008-10-24 19:15 ` Sam Ravnborg
2008-10-24 23:44 ` Alistair John Strachan
2008-10-24 17:09 ` Matt Mackall
2008-10-24 17:54 ` Matt Mackall
2008-10-24 17:57 ` Randy Dunlap
2008-10-24 18:05 ` Fenghua Yu
2008-10-24 18:11 ` Matt Mackall
2008-10-24 18:59 ` 2.6.28-rc1: EIP: slab_destroy+0x84/0x142 Alexey Dobriyan
2008-10-24 21:38 ` Matt Mackall
2008-10-24 22:09 ` Alexey Dobriyan
2008-10-24 23:29 ` Christoph Lameter
2008-10-25 0:24 ` Alexey Dobriyan
2008-10-25 0:30 ` Matt Mackall
2008-10-25 2:54 ` Alexey Dobriyan
2008-10-25 3:00 ` Matt Mackall
2008-10-25 3:20 ` Alexey Dobriyan
2008-10-26 12:30 ` Avi Kivity
2008-10-26 21:27 ` Alexey Dobriyan
2008-10-27 14:23 ` Alexey Dobriyan
2008-10-27 14:24 ` Avi Kivity
2008-10-24 22:28 ` nf_conntrack oopes on parisc/smp (was Re: Linux 2.6.28-rc1) Domenico Andreoli
2008-10-24 22:53 ` Linux 2.6.28-rc1 Tony Vroon
2008-10-24 23:01 ` Arjan van de Ven
2008-10-26 13:17 ` Tony Vroon
2008-10-30 14:26 ` 2.6.28-rc1: NVRAM being corrupted on ppc64 preventing boot (bisected) Mel Gorman
2008-10-30 14:26 ` Mel Gorman
2008-10-30 20:52 ` Paul Mackerras
2008-10-30 20:52 ` Paul Mackerras
2008-10-30 21:05 ` Josh Boyer
2008-10-30 21:05 ` Josh Boyer
2008-10-30 21:35 ` Dave Kleikamp
2008-10-30 21:35 ` Dave Kleikamp
2008-10-31 10:36 ` Mel Gorman
2008-10-31 10:36 ` Mel Gorman
2008-10-31 11:10 ` Paul Mackerras
2008-10-31 11:10 ` Paul Mackerras
2008-10-31 11:31 ` Mel Gorman
2008-10-31 11:31 ` Mel Gorman
2008-10-31 18:36 ` Mel Gorman
2008-10-31 18:36 ` Mel Gorman
2008-10-31 11:18 ` Paul Mackerras
2008-10-31 11:18 ` Paul Mackerras
2008-10-31 11:31 ` Benjamin Herrenschmidt
2008-10-31 11:31 ` Benjamin Herrenschmidt
2008-10-31 11:56 ` Paul Mackerras
2008-10-31 11:56 ` Paul Mackerras
2008-10-31 11:32 ` Mel Gorman
2008-10-31 11:32 ` Mel Gorman
-- strict thread matches above, loose matches on Subject: below --
2008-10-24 18:10 Linux 2.6.28-rc1 Rufus & Azrael
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=200810241352.45745.alistair@devzero.co.uk \
--to=alistair@devzero.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.