linux-kernel - Re: kernel building procedure changed?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090222230031.GB30619@uranus.ravnborg.org>
Date:	Mon, 23 Feb 2009 00:00:31 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Jiri Slaby <jirislaby@...il.com>
Cc:	Cyrill Gorcunov <gorcunov@...il.com>, Ingo Molnar <mingo@...e.hu>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: kernel building procedure changed?

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@...ovo 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?
Does it happen with mainline?
I need to know what tree to look at - and I do not have mmotm handy.

	Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/