unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Matthias Wachs <wachs@net.in.tum.de>
Cc: guix-devel@gnu.org
Subject: Re: Compiling guix 0.3 on a fedora 8 planetlab node
Date: Thu, 29 Aug 2013 22:02:46 +0200	[thread overview]
Message-ID: <87ob8g9sex.fsf@gnu.org> (raw)
In-Reply-To: <521F6CE7.60804@gmail.com> (Cyril Roelandt's message of "Thu, 29 Aug 2013 17:46:47 +0200")

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 “no”, 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’t be a problem in practice.

HTH,
Ludo’.

  reply	other threads:[~2013-08-29 20:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-28 15:45 Compiling guix 0.3 on a fedora 8 planetlab node Matthias Wachs
2013-08-29 15:46 ` Cyril Roelandt
2013-08-29 20:02   ` Ludovic Courtès [this message]
2013-08-29 20:13     ` Andreas Enge
2013-08-29 20:15       ` Andreas Enge
2013-08-29 21:31         ` Ludovic Courtès
2013-08-30 10:01           ` Matthias Wachs
2013-08-30 11:09             ` Ludovic Courtès
2013-08-30 11:18               ` Matthias Wachs
2013-08-30 12:05                 ` Ludovic Courtès
2013-08-31  9:37                   ` Mark H Weaver
2013-09-10  7:14           ` Matthias Wachs
2013-09-10 17:37             ` Ludovic Courtès

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ob8g9sex.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=wachs@net.in.tum.de \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).