unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: eisbaer@tilde.team
Cc: help-guix@gnu.org
Subject: Re: Custom kernel config is not taken by guix
Date: Tue, 04 Apr 2023 13:54:53 +0000	[thread overview]
Message-ID: <871qkzbura.fsf@kitej> (raw)
In-Reply-To: <5d0a15e9ab3f8ce31577650959327c950d215fec@tilde.team>

[-- Attachment #1: Type: text/plain, Size: 2425 bytes --]

eisbaer@tilde.team skribis:

> Thanks a lot for your reply. Your example did not work on my machine. I adjusted my config.scm as you said but the guix systemc reconfigure did not run through... 
>
>
> ========================
> error in  /var/log/guix/drvs/jr/88fpnzh0kc7w7vwjz78b501sdy2jcg-linux-libre-6.1.15.drv.gz
> ========================
> [...]
> error: in phase 'configure': uncaught exception:
> misc-error #f "~A ~S" ("Mismatching configurations in .config and arch/x86/configs/guix_defconfig" (("CONFIG_DEBUG_INFO" (#f "y")))) #f 
> phase `configure' failed after 14.2 seconds
> Backtrace:
>            8 (primitive-load "/gnu/store/a2kzfabrb2qrj85xq5z8fnkg9z5…")
> In guix/build/gnu-build-system.scm:
>     906:2  7 (gnu-build #:source _ #:outputs _ #:inputs _ #:phases . #)
> In ice-9/boot-9.scm:
>   1752:10  6 (with-exception-handler _ _ #:unwind? _ # _)
> In srfi/srfi-1.scm:
>     634:9  5 (for-each #<procedure 7ffff6107740 at guix/build/gnu-b…> …)
> In ice-9/boot-9.scm:
>   1752:10  4 (with-exception-handler _ _ #:unwind? _ # _)
> In guix/build/gnu-build-system.scm:
>    927:23  3 (_)
> In guix/build/kconfig.scm:
>     174:6  2 (verify-config ".config" "arch/x86/configs/guix_defconf…")
> In ice-9/boot-9.scm:
>   1685:16  1 (raise-exception _ #:continuable? _)
>   1685:16  0 (raise-exception _ #:continuable? _)
>
> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
> Mismatching configurations in .config and arch/x86/configs/guix_defconfig (("CONFIG_DEBUG_INFO" (#f "y")))

Hi.
Using the 'customize-linux' function with the '#:configs' keyword just
adds the specified options to the config file. In this case it
looks like there are other options in the config file that are not
compatible with the added CONFIG_DEBUG_INFO option.

So I think you will have to make a kernel config file with the options
you want using a regular kernel configurator (e.g. "make menuconfig",
"make xconfig" etc in the kernel source tree). Then you should be able
to use this custom config file with the '#:defconfig' keyword:

--8<---------------cut here---------------start------------->8---
(define linux-libre-debug
  (customize-linux #:linux linux-libre
                   #:defconfig (local-file "/path/to/custom/config")))

(operating-system
  (kernel linux-libre-debug)
  ...)
--8<---------------cut here---------------end--------------->8---

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  parent reply	other threads:[~2023-04-04 14:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22 16:07 Custom kernel config is not taken by guix eisbaer
2023-04-01 11:35 ` Guillaume Le Vaillant
     [not found] ` <5d0a15e9ab3f8ce31577650959327c950d215fec@tilde.team>
2023-04-04 13:54   ` Guillaume Le Vaillant [this message]
2023-04-04 18:34   ` eisbaer
2023-04-05 12:14     ` Guillaume Le Vaillant

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=871qkzbura.fsf@kitej \
    --to=glv@posteo.net \
    --cc=eisbaer@tilde.team \
    --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).