From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: Compiling guix 0.3 on a fedora 8 planetlab node
Date: Thu, 29 Aug 2013 22:02:46 +0200
Message-ID: <87ob8g9sex.fsf@gnu.org>
References: <1377704712.3250.69.camel@fulcrum.net.in.tum.de>
	<521F6CE7.60804@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:60678)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1VF8Vd-0000yl-2l
	for guix-devel@gnu.org; Thu, 29 Aug 2013 16:08:07 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1VF8VW-0008Em-F8
	for guix-devel@gnu.org; Thu, 29 Aug 2013 16:08:00 -0400
Received: from hera.aquilenet.fr ([141.255.128.1]:53900)
	by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <ludo@gnu.org>)
	id 1VF8VW-0008Ei-8q
	for guix-devel@gnu.org; Thu, 29 Aug 2013 16:07:54 -0400
In-Reply-To: <521F6CE7.60804@gmail.com> (Cyril Roelandt's message of "Thu, 29
	Aug 2013 17:46:47 +0200")
List-Id: <guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
To: Matthias Wachs <wachs@net.in.tum.de>
Cc: guix-devel@gnu.org

Hi Matthias,

Cyril Roelandt <tipecaml@gmail.com> skribis:

> On 08/28/2013 05:45 PM, Matthias Wachs wrote:
>> Hi,
>>
>
> Hi!
>
>> I am trying to compile guix 0.3 on very old fedora core 8 system.
>>
>
> This is quite an old system: CLONE_NEWPID and CLONE_NEWNET were
> introduced in Linux 2.6.24, CLONE_NEWIPC and CLONE_NEWUTS were
> introduced in Linux 2.6.19.

Indeed.

> Isn't there any way for you to use a more recent kernel ?

If the answer is =E2=80=9Cno=E2=80=9D, then you may just as well comment out
CLONE_NEWIPC in nix/libstore/build.cc.

The effect is that the build environment will share the same IPC name
space as the outside world, which could interfere when building stuff
that uses SysV IPC.  Hopefully, that won=E2=80=99t be a problem in practice.

HTH,
Ludo=E2=80=99.