From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Vagrant Cascadian <vagrant@debian.org>, 31447@debbugs.gnu.org
Subject: [bug#31447] [PATCH] linux-libre: Add aarch64-linux.
Date: Thu, 17 May 2018 14:44:33 -0400 [thread overview]
Message-ID: <87d0xu5dgu.fsf@netris.org> (raw)
In-Reply-To: <87lgci4q90.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 17 May 2018 10:53:47 +0200")
Hi!
ludo@gnu.org (Ludovic Courtès) writes:
>> From b9e48a787b6b151b5c7df6036eb75752d3c4db24 Mon Sep 17 00:00:00 2001
>> From: Vagrant Cascadian <vagrant@debian.org>
>> Date: Mon, 14 May 2018 03:20:17 +0000
>> Subject: [PATCH] gnu: linux-libre: Enable build for aarch64-linux.
>>
>> * gnu/packages/linux.scm (%linux-compatible-systems): Add aarch64-linux.
>> * gnu/packages/aux-files/linux-libre/4.16-arm64.conf: New file.
>
> I think we should add the .conf file to gnu/local.mk, but apart from
> that it LGTM.
>
> Mark, WDYT?
%linux-compatible-systems is also used as the 'supported-systems' field
of linux-libre-4.14, but there's no '4.14-arm64.conf' file added here.
We should either add that file, or else somehow arrange for
'aarch64-linux' to be omitted from linux-libre-4.14's
'supported-systems' field.
As Ludovic mentioned, the new .conf file needs to be added to
gnu/local.mk.
Otherwise, it looks good to me.
Thank you!
Mark
next prev parent reply other threads:[~2018-05-17 18:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 3:40 [bug#31447] [PATCH] linux-libre: Add aarch64-linux Vagrant Cascadian
2018-05-17 8:53 ` Ludovic Courtès
2018-05-17 18:44 ` Mark H Weaver [this message]
2018-05-17 22:05 ` Vagrant Cascadian
2018-05-18 4:38 ` Mark H Weaver
2018-05-18 22:31 ` Vagrant Cascadian
2018-05-19 23:33 ` Vagrant Cascadian
2018-05-20 22:11 ` Ludovic Courtès
2018-05-20 22:26 ` Vagrant Cascadian
2018-05-20 22:12 ` bug#31447: " 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=87d0xu5dgu.fsf@netris.org \
--to=mhw@netris.org \
--cc=31447@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=vagrant@debian.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).