From: Alexander Dahl <ada@thorsis.com>
To: linux-rt-users@vger.kernel.org
Cc: Gene Heskett <gheskett@shentel.net>
Subject: Re: [ANNOUNCE] v5.4.10-rt5
Date: Tue, 14 Jan 2020 09:01:27 +0100 [thread overview]
Message-ID: <1896107.FrWXgdeJfy@ada> (raw)
In-Reply-To: <202001122122.10938.gheskett@shentel.net>
Hello Gene,
Am Sonntag, 12. Januar 2020, 21:22:10 CET schrieb Gene Heskett:
> I grabbed a copy of this, then turned off anything not needed to run
> LinuxCNC on an rpi4 in armhf config. Then I noted its make had a make
> deb-pkg option. But it isn't making what I told it to make as I'm
> sitting here watching it ALL go by. Did I miss something in a make
> menuconfig that triggered a make all? It was supposedly set for armhf.
> But I'm even seeing x86 stuff go by. Obviously I know just enough to
> screw it up. Point me at the right docs for arm builds please.
Building a RT kernel is no different than building any other kernel with
patches. Patch your kernel source, configure, compile …
You can use any howto or docs for building the kernel for your platform.
Speaking of RPi4, it depends on your Linux distribution and whether you
compile on the target or do cross compiling from another machine. But if you
got this sorted out, you just need to apply the RT patch and build again.
However this list is probably not the right place for that sort of questions.
HTH & Greets
Alex
next prev parent reply other threads:[~2020-01-14 8:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 20:14 [ANNOUNCE] v5.4.10-rt5 Sebastian Andrzej Siewior
2020-01-13 2:22 ` Gene Heskett
2020-01-14 8:01 ` Alexander Dahl [this message]
2020-01-14 13:56 ` Paul Thomas
[not found] ` <CAD56B7cgPfbcx8MNtYosOwhPi6fy+fqdauLsayR65dAg1yaYSg@mail.gmail.com>
2020-01-14 16:23 ` Gene Heskett
2020-01-14 17:15 ` Paul Thomas
2020-01-14 21:03 ` Gene Heskett
2020-01-14 21:26 ` Paul Thomas
2020-01-14 23:10 ` Gene Heskett
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=1896107.FrWXgdeJfy@ada \
--to=ada@thorsis.com \
--cc=gheskett@shentel.net \
--cc=linux-rt-users@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).