unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Filipe Brandenburger <filbranden@google.com>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org, linux-numa@vger.kernel.org
Subject: Re: Build failure on armhf
Date: Wed, 30 Dec 2015 09:06:46 -0800	[thread overview]
Message-ID: <CADU+-uBzna7Gv=Oo50=zo-Ti2e6rjeJEEQys2fns5FT8eFw1hw@mail.gmail.com> (raw)
In-Reply-To: <20151212135721.GA18797@debian>

Hi Andreas,

On Sat, Dec 12, 2015 at 5:57 AM, Andreas Enge <andreas@enge.fr> wrote:
> numactl fails to build on armhf:
>    http://hydra.gnu.org/build/866208/log/raw
> with the following error message:
> syscall.c:113:2: error: #error "Add syscalls for your architecture or update kernel headers"
>  #error "Add syscalls for your architecture or update kernel headers"
>
> Is this a known limitation?

So syscall.c defines the syscall numbers for syscalls such as
set_mempolicy, migrate_pages, etc. The syscalls numbers are different
on different Linux platforms, so it's only currently defined for a
handful of platforms.

As the error message says, if you find that error, maybe you should
consider adding the syscall numbers for your platform there?

> If yes, could it maybe be detected during the
> call to "configure"?

The detection is fairly complex, it mainly depends on compiler macros
being defined for your platform. Furthermore, adding platform
detection code to configure would probably create duplication, in that
both configure.ac and syscalls.c would need to be updated to add
support for a new platform.

What is the problem you are trying to solve?

Cheers,
Filipe

  reply	other threads:[~2015-12-30 17:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-12 13:57 Build failure on armhf Andreas Enge
2015-12-30 17:06 ` Filipe Brandenburger [this message]
2015-12-30 19:45   ` Andi Kleen
2016-01-21 20:12     ` Andreas Enge

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='CADU+-uBzna7Gv=Oo50=zo-Ti2e6rjeJEEQys2fns5FT8eFw1hw@mail.gmail.com' \
    --to=filbranden@google.com \
    --cc=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=linux-numa@vger.kernel.org \
    /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).