From: phodina <phodina@protonmail.com>
To: "André A. Gomes" <andremegafone@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Custom libre kernel configuration
Date: Thu, 11 Nov 2021 13:08:52 +0000 [thread overview]
Message-ID: <Z-eKFPfDOxqV7BLyjklGbkmd02ao89YrSTVoSs1NX8Iem80mnratLZQsTMDGrwQBYokP1XnfMKA5DBTGj0gtdpmKx5rTKLyTWrtaJIsnPxA=@protonmail.com> (raw)
In-Reply-To: <87bl2qq2lj.fsf@gmail.com>
Hi Andre,
On Thursday, November 11th, 2021 at 1:49 PM, André A. Gomes <andremegafone@gmail.com> wrote:
> phodina phodina@protonmail.com writes:
>
> > --- a/gnu/packages/linux.scm
> >
> > +++ b/gnu/packages/linux.scm
> >
> > @@ -722,6 +722,14 @@ (define %bpf-extra-linux-options
> >
> > ;; kheaders module
> >
> > ("CONFIG_IKHEADERS" . #t)))
>
> Isn't there an extra closing parenthesis on this s-exp?
>
Unfortunately no. If I leave only CONFIG_ASHMEM and CONFIG_ANDROID_BINDER_IPC the kernel builds.
Then again when I check the kernel menuconfig the other options are present, but for some reason Guix fails.
Petr
next prev parent reply other threads:[~2021-11-11 13:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 12:31 Custom libre kernel configuration phodina
2021-11-11 12:49 ` André A. Gomes
2021-11-11 13:08 ` phodina [this message]
2021-11-11 13:23 ` Tobias Geerinckx-Rice
2021-11-11 14:13 ` phodina
2021-11-11 15:01 ` Tobias Geerinckx-Rice
2021-11-11 15:19 ` phodina
2021-11-12 23:38 ` Tobias Geerinckx-Rice
2021-11-13 8:08 ` phodina
2021-11-13 12:23 ` Custom libre kernel configuration devolving into Anbox review I guess Tobias Geerinckx-Rice
2021-11-13 13:44 ` Tobias Geerinckx-Rice
2021-11-14 7:13 ` phodina
-- strict thread matches above, loose matches on Subject: below --
2021-11-13 12:35 Custom libre kernel configuration Stefan
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='Z-eKFPfDOxqV7BLyjklGbkmd02ao89YrSTVoSs1NX8Iem80mnratLZQsTMDGrwQBYokP1XnfMKA5DBTGj0gtdpmKx5rTKLyTWrtaJIsnPxA=@protonmail.com' \
--to=phodina@protonmail.com \
--cc=andremegafone@gmail.com \
--cc=help-guix@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).