linux-kernel - Re: linux-next: kbuild-current build failure

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]

Date:	Tue, 10 Jun 2008 06:33:48 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus <torvalds@...ux-foundation.org>
Subject: Re: linux-next: kbuild-current build failure

On Tue, Jun 10, 2008 at 11:08:42AM +1000, Stephen Rothwell wrote:
> Hi Sam,
> 
> Today's linux-next build (powerpc ppc64_deconfig) failed like this:
> 
>   LD      vmlinux.o
> /scratch/sfr/next/scripts/Makefile.modpost:44: scripts/Kbuild.include: No such file or directory
> /scratch/sfr/next/scripts/Makefile.modpost:58: scripts/Makefile.lib: No such file or directory
> make[2]: *** No rule to make target `scripts/Makefile.lib'.  Stop.
> make[1]: *** [vmlinux] Error 2
> make: *** [sub-make] Error 2

Ups - I have not doen O=.. builds...

> 
> This is Linus' tree with just the net-current, arm-current and
> kbuild-current trees merged i.e. just bug fixes queued for Linus' current
> tree.  The build was done with "O=../powerpc_ppc64_defconfig -j24 -s"
> i.e. separate object tree and parallel.
> 
> Reverting commit 68e9b79c8dad5245f28ab4f3527481b730dbdb61 ("kbuild:
> simplify vmlinux link stage") makes the build work again.

This commit is in kbuild-next.git (for the merge window)
My kbuild-fixes.git is empty at the moment.

I will fix tonight.

	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/