[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Custom kernel

From: Ludovic Courtès
Subject: Re: Custom kernel
Date: Mon, 05 Dec 2016 10:33:15 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux)

"Dmitri Anikin" <address@hidden> skribis:

> December 2, 2016 2:50 PM, address@hidden wrote:
>> Hello Dmitri,
>> "Dmitri Anikin" <address@hidden> skribis:
>>> Is it possible to pass custom patches and kernel config file to be used for 
>>> linux-libre package?
>> It is possible, yes.
>> If you look at (gnu packages linux), you’ll find this:
>> (define* (kernel-config arch #:key variant)
>> "Return the absolute file name of the Linux-Libre build configuration file
>> for ARCH and optionally VARIANT, or #f if there is no such configuration."
>> …)
>> (define* (make-linux-libre version hash supported-systems
>> #:key
>> ;; A function that takes an arch and a variant.
>> ;; See kernel-config for an example.
>> (extra-version #f)
>> (configuration-file #f)
>> (defconfig "defconfig")
>> (extra-options %default-extra-linux-options)
>> (patches (list %boot-logo-patch)))
>> (package
>> …))
>> and later:
>> (define-public linux-libre
>> (make-linux-libre "4.8.11"
>> "04h3n3lw563i4yhxfkxrrwjvafd3af730l1ih9kqv7qwkm0psy7r"
>> %intel-compatible-systems
>> #:configuration-file kernel-config))
>> Currently ‘make-linux-libre’ is not public, but we could probably make
>> it public (David, WDYT?). In the meantime, in your own module, you can
>> do:
>> (define make-linux-libre
>> ;; It’s private but I wanna use it anyway!
>> (@@ (gnu packages linux) make-linux-libre))
>> HTH!
>> Ludo’.
> When I try guix build -f linux.scm --no-build-hook I get this error
>>source is under 'linux-4.8'
>>applying '/gnu/store/dhq2gd73qaqirc6a4pj5yr537s76sj36-patch-4.8-pf8.patch'...
>>builder for 
>>failed to produce output path 

If you look higher in the build log, there’s probably an error message
from ‘patch’ indicating that it failed to apply one of the patches.
Could you check that?

You can access the full log by opening the file returned by:

  guix build --log-file 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]