From: Efraim Flashner <efraim@flashner.co.il>
To: radoslaw@chmielarz.xyz
Cc: help-guix@gnu.org
Subject: Re: Guix and sel4
Date: Mon, 15 Jan 2018 23:18:12 +0200 [thread overview]
Message-ID: <20180115211812.GA1157@macbook41> (raw)
In-Reply-To: <9b985bf236a0f43870259bf105f6f36d@chmielarz.xyz>
[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]
On Mon, Jan 15, 2018 at 09:44:08PM +0100, radoslaw@chmielarz.xyz wrote:
> Hi,
>
> It wasn't entirely what I was hoping for but thank You for answering. So to
> dig a little deeper how closely is guix connected to linux kernel? In other
> words what would have to be changed in order to work with a different kernel
> and therefore different syscalls? I don't mean the whole system but the
> minimal set. I would assume that a toolchain (make, binutils, gcc),
> obviously guile if there is anything specific to linux in it. Anything else?
>
> Cheers,
> Radek
>
from 'git grep linux-{libre-}headers' it comes up a few times, but
really in make-boostrap, cross-base and commencement. For a start I
would focus on make-bootstrap (to make the boostrap binaries) and then
commencement (to build up again).
As far as different syscalls, I assume mist things should just work, but
I haven't looked into it.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-15 21:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-14 21:16 Guix and sel4 radoslaw
2018-01-14 23:26 ` Paul Boddie
2018-01-15 20:44 ` radoslaw
2018-01-15 21:17 ` Paul Boddie
2018-01-15 21:18 ` Efraim Flashner [this message]
2018-01-16 16:23 ` Ludovic Courtès
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=20180115211812.GA1157@macbook41 \
--to=efraim@flashner.co.il \
--cc=help-guix@gnu.org \
--cc=radoslaw@chmielarz.xyz \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).