All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Cyrill Gorcunov <gorcunov@gmail.com>, Ingo Molnar <mingo@elte.hu>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: kernel building procedure changed?
Date: Mon, 23 Feb 2009 00:15:50 +0100	[thread overview]
Message-ID: <49A1DCA6.30000@gmail.com> (raw)
In-Reply-To: <20090222230031.GB30619@uranus.ravnborg.org>

On 23.2.2009 00:00, Sam Ravnborg wrote:
> On Sun, Feb 22, 2009 at 11:27:51PM +0100, Jiri Slaby wrote:
>> On 22.2.2009 23:16, Sam Ravnborg wrote:
>>> On Mon, Feb 23, 2009 at 01:07:48AM +0300, Cyrill Gorcunov wrote:
>>>> Hi all,
>>>>
>>>> I found a bit strange thing happens now --
>>>> plain
>>>>
>>>> 	make arch/x86/kernel/head64.o
>>>>
>>>> doesn't work anymore. Instead of compiling
>>>> _just_ this file I've got the following:
>>>>
>>>> ---
>>>> cyrill@lenovo linux-2.6.git $ make arch/x86/kernel/head64.o
>>>>    CHK     include/linux/version.h
>>>>    CHK     include/linux/utsrelease.h
>>>>    SYMLINK include/asm ->   include/asm-x86
>>>>    CALL    scripts/checksyscalls.sh
>>>>    CHK     include/linux/compile.h
>>>>    AS      arch/x86/kernel/head_64.o
>>>>    VDSOSYM arch/x86/vdso/vdso-syms.lds
>>>>    VDSOSYM arch/x86/vdso/vdso32-int80-syms.lds
>>>>    VDSOSYM arch/x86/vdso/vdso32-syscall-syms.lds
>>>>    VDSOSYM arch/x86/vdso/vdso32-sysenter-syms.lds
>>>>    VDSOSYM arch/x86/vdso/vdso32-syms.lds
>>>>    LD      arch/x86/vdso/built-in.o
>>>>    CC      fs/hpfs/dnode.o
>>>> make[2]: *** [fs/hpfs/dnode.o] Interrupt
>>>> make[1]: *** [fs/hpfs] Interrupt
>>>> make: *** [fs] Interrupt
>>>> ---
>>>>
>>>> I've done make allyesconfig previously.
>>>> I don't understand what I'm doing wrong... :(
>>> I should work...
>> It is matter of days, new mmotm doesn't work either, older did.
>
> Does it happen with -next?

yes, aa0f1f110f4cbbbb83fbac36f71651b232cd8b32

> Does it happen with mainline?

yes, 683fdc5fe5fec5c4f27eb58a8781f212f50c8e01

> I need to know what tree to look at - and I do not have mmotm handy.

some of -tip too, 8075257261ba779bfc81bec4b633a3984617cdd5 -- this sha 
posted me Cyrill before he left.

  reply	other threads:[~2009-02-22 23:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-22 22:07 kernel building procedure changed? Cyrill Gorcunov
2009-02-22 22:13 ` Jesper Juhl
2009-02-22 22:16 ` Sam Ravnborg
2009-02-22 22:27   ` Jiri Slaby
2009-02-22 23:00     ` Sam Ravnborg
2009-02-22 23:15       ` Jiri Slaby [this message]
2009-02-23  7:48       ` Cyrill Gorcunov
2009-02-23  8:14         ` Cyrill Gorcunov
2009-02-22 22:28   ` Cyrill Gorcunov

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=49A1DCA6.30000@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=gorcunov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sam@ravnborg.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.