From: Andi Kleen <andi@firstfloor.org>
To: Filipe Brandenburger <filbranden@google.com>
Cc: Andreas Enge <andreas@enge.fr>,
linux-numa@vger.kernel.org, guix-devel@gnu.org
Subject: Re: Build failure on armhf
Date: Wed, 30 Dec 2015 20:45:04 +0100 [thread overview]
Message-ID: <20151230194503.GF15533@two.firstfloor.org> (raw)
In-Reply-To: <CADU+-uBzna7Gv=Oo50=zo-Ti2e6rjeJEEQys2fns5FT8eFw1hw@mail.gmail.com>
> What is the problem you are trying to solve?
I guess he wants to build on that platform.
Adding the numbers to syscall.c is also only needed if the necessary
syscall numbers are missing in asm/unistd.h. It really was originally
only for ancient distributions where the headers predate numa support.
So updating that may also help.
If your headers don't have numa support at all it may be also possible
that the platform simply doesn't support NUMA. In that case building
numactl is pointless.
-Andi
next prev parent reply other threads:[~2015-12-30 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-12 13:57 Build failure on armhf Andreas Enge
2015-12-15 8:56 ` Andreas Enge
2015-12-30 17:06 ` Filipe Brandenburger
2015-12-30 19:45 ` Andi Kleen [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151230194503.GF15533@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=andreas@enge.fr \
--cc=filbranden@google.com \
--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.
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 NNTP newsgroup(s).