All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: John Kacur <jkacur@redhat.com>
Cc: linux-rt-users@vger.kernel.org, Clark Williams <williams@redhat.com>
Subject: Re: [rteval] Fails to work without numactl
Date: Tue, 31 Aug 2021 09:14:36 +0200	[thread overview]
Message-ID: <20210831071436.w7ahd7twa52qcbvn@linutronix.de> (raw)
In-Reply-To: <67ce47c9-1631-bf20-8477-f6de91775062@redhat.com>

On 2021-08-30 16:33:32 [-0400], John Kacur wrote:
> What distro are you running on Sebastian?
Debian but I didn't install it in anyway. I just run make of the git
checkout and this started it if I remember correctly.

> In rpm based distros numactl is a Requires, so that path where it is not 
> available is rarely tested - but that doesn't mean I won't take a patch or 
> try to fix it myself. I did have a quick look at it.

From the checkout there were complains about other libs but nothing
complained about numactl. Thanks.

> kcompile.py compiles an allmodconfig kernel. (not sure this is the best 
> thing to do still, but that's a different topic)
> 
> The requirements for that continues to grow. I have often seen rteval fail
> when requirements for building the kernel aren't installed on a machine.

okay.

> You can usually figure that out by looking at the debug logs in rteval, 
> but another simple thing to do is simply try an allmodconfig kernel 
> compile on your machine and when it fails figure out what 
> software is needed. It wouldn't be a bad thing to have a list of Debian 
> build requirements and Fedora build requirements, etc.

Okay.

> John

Sebastian

      reply	other threads:[~2021-08-31  7:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-16 11:58 [rteval] Fails to work without numactl Sebastian Andrzej Siewior
2021-08-30 19:51 ` Sebastian Andrzej Siewior
2021-08-30 20:33   ` John Kacur
2021-08-31  7:14     ` Sebastian Andrzej Siewior [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

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

  git send-email \
    --in-reply-to=20210831071436.w7ahd7twa52qcbvn@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=jkacur@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.