unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Matthias Wachs <wachs@net.in.tum.de>
Cc: 15209@debbugs.gnu.org, request@debbugs.gnu.org
Subject: bug#15209: guix 0.3 does not compile on fedora core 8 nodes
Date: Mon, 30 Dec 2013 17:03:26 +0100	[thread overview]
Message-ID: <878uv2e375.fsf@gnu.org> (raw)
In-Reply-To: <87a9jz4pij.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 30 Aug 2013 09:16:36 +0200")

tag 15209 wontfix
retitle 15209 Daemon fails to build with Linux < 2.6.24
thanks

ludo@gnu.org (Ludovic Courtès) skribis:

> Matthias Wachs <wachs@net.in.tum.de> skribis:
>
>> +#ifndef CLONE_NEWPID
>> +#define CLONE_NEWPID            0x20000000      /* New pid namespace */
>> +#endif
>> +#ifndef CLONE_NEWNET
>> +#define CLONE_NEWNET            0x40000000      /* New network namespace */
>> +#endif 
>> +#ifndef CLONE_NEWIPC
>> +#define CLONE_NEWIPC            0x08000000      /* New ipcs */
>> +#endif 
>> +#ifndef CLONE_NEWUTS
>> +#define CLONE_NEWUTS            0x04000000      /* New utsname group? */
>> +#endif 
>
> I’m reluctant to adding such a patch because (1) as was already
> mentioned, these features are missing only on very old kernels, and
> (2) if the libc headers don’t define these flag, chances are that
> clone(2) doesn’t support them anyway.
>
> WDYT?

Marking as ‘wontfix’.  Let us know if this is a problem.

Thanks,
Ludo’.

      reply	other threads:[~2013-12-30 16:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29 13:54 bug#15209: guix 0.3 does not compile on fedora core 8 nodes Matthias Wachs
2013-08-30  7:16 ` Ludovic Courtès
2013-12-30 16:03   ` Ludovic Courtès [this message]

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=878uv2e375.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=15209@debbugs.gnu.org \
    --cc=request@debbugs.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).