From: John Kacur <jkacur@redhat.com>
To: Javier Sanz <jsanza@gmail.com>
Cc: RT <linux-rt-users@vger.kernel.org>,
Clark Williams <williams@redhat.com>
Subject: Re: numa.h for rt-test
Date: Tue, 27 Oct 2015 10:18:51 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.20.1510271018100.5915@riemann.fritz.box> (raw)
In-Reply-To: <alpine.LFD.2.20.1510270946570.5915@riemann.fritz.box>
On Tue, 27 Oct 2015, John Kacur wrote:
>
>
> On Mon, 26 Oct 2015, Javier Sanz wrote:
>
> > Sorry,
> >
> > make NUMA=0
> >
> > Tx
> >
> > 2015-10-26 11:56 GMT+01:00 Javier Sanz <jsanza@gmail.com>:
> > > Hello,
> > >
> > > I am trying to compile rt-tests-0.96 and i got :
> > >
> > > root@darkstar rt-tests-0.96]# make
> > > gcc -D VERSION=0.96 -c src/cyclictest/cyclictest.c -Wall -Wno-nonnull
> > > -O2 -DNUMA -D_GNU_SOURCE -Isrc/include -o bld/cyclictest.o
> > > In file included from src/cyclictest/cyclictest.c:39:0:
> > > src/cyclictest/rt_numa.h:29:18: fatal error: numa.h: No such file or directory
> > > compilation terminated.
> > > Makefile:87: recipe for target 'bld/cyclictest.o' failed
> > > make: *** [bld/cyclictest.o] Error 1
> > > [root@darkstar rt-tests-0.96]#
> > >
> > >
> > > why do i need to get numa.h ??
> > >
> > > Tx
> > --
>
> I think the original thinking was that it is a trivial thing to install
> the numa libs even if you are not going to use them, but I have personally
Should read, "I have NEVER liked this" :)
> liked this. I could imagine that this requirement is not
> always so simple in the embedded space. I'll look into seeing if I can
> remove this. (or try yourself, and send me a patch.)
>
> Thanks
>
> John
>
next prev parent reply other threads:[~2015-10-27 9:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 10:56 numa.h for rt-test Javier Sanz
2015-10-26 11:05 ` Javier Sanz
2015-10-27 8:49 ` John Kacur
2015-10-27 9:18 ` John Kacur [this message]
2015-10-26 12:45 ` Jeff Epler
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=alpine.LFD.2.20.1510271018100.5915@riemann.fritz.box \
--to=jkacur@redhat.com \
--cc=jsanza@gmail.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@redhat.com \
/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).