linux-kernel - Re: linux-next: Tree for Feb 7 (fakeroot BROKEN due to SYSV IPC support?)

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CA+icZUXzh1S2+ZQ8vvPFSN8jXS62kijbAP+83F0hG9emLQzpQw@mail.gmail.com>
Date:	Thu, 7 Feb 2013 10:38:02 +0100
From:	Sedat Dilek <sedat.dilek@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: Tree for Feb 7 (fakeroot BROKEN due to SYSV IPC support?)

On Thu, Feb 7, 2013 at 7:37 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi all,
>
> Changes since 20130206:
>
> Removed tree: kvmtool (still present via the tip tree)
>
> The block tree lost its build failure.
>
> The tip tree gained a conflict against the s390 tree.
>
> The kvm tree gained a conflict against Linus' tree.
>
> The tty tree lost its build failure.
>
> The arm-soc tree gained conflicts against the iommu tree.
>
> The signal tree gained a conflict against the s390 tree.
>
> The akpm tree gained a conflict against the kvm tree and lost its build
> failure.
>
> ----------------------------------------------------------------------------
>

My build-script uses fakeroot and does no more start:

$ ./scripts/build_linux-next.sh
make options ...... CC=gcc-4.6 -j4
KBUILD_BUILD_USER=sedat.dilek@...il.com
LOCALVERSION=-next20130207-2-iniza-small
dep-pkg options ... KDEB_PKGVERSION=3.8.0~rc6~next20130207-2~iniza+dileks1
fakeroot, while creating message channels: Invalid argument
This may be due to a lack of SYSV IPC support.
fakeroot: error while starting the `faked' daemon.
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec
... or kill -l [sigspec]

Any hints?
( I could run strace... )

- Sedat -

Download attachment "build_linux-next.sh" of type "application/x-sh" (3852 bytes)