all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Rustand <rustand.lars@gmail.com>
To: 68059@debbugs.gnu.org
Subject: bug#68059: Mismatching defconfig options
Date: Wed, 27 Dec 2023 09:35:45 +0100	[thread overview]
Message-ID: <87il4kjagi.fsf@yoga.mail-host-address-is-not-set> (raw)


I'm having trouble building a custom kernel with an included
defconfig. The kernel builds correctly with the included defconfig if I
do it manually, but when I try to build it through Guix I get an error
about Mismatching configurations in .config and
arch/arm64/configs/guix_defconfig.

Since it builds correctly manually I am sure that the defconfig does in
fact work, and it does not have any mismatching configuration. So it
must be something that Guix adds/changes in the defconfig that makes it
stop working. How can I prevent Guix from modifying the defconfig that I
tell it to use?

Here is the relevant part of my package definition:

--8<---------------cut here---------------start------------->8---
(let ((linux-package
       (customize-linux
        #:name name
        #:linux linux
        #:defconfig
        "pinephone_pro_defconfig"
        #:extra-version "arm64-pinephone-pro"
        #:source (origin (method url-fetch)
                         (uri (linux-pinephone-urls version))
                         (sha256 (base32 hash)))))))
--8<---------------cut here---------------end--------------->8---




             reply	other threads:[~2023-12-27 14:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-27  8:35 Lars Rustand [this message]
2023-12-27 16:55 ` bug#68059: Mismatching defconfig options Josselin Poiret via Bug reports for GNU Guix
2023-12-30 10:39   ` Lars Rustand
2024-01-12 10:17     ` Josselin Poiret via Bug reports for GNU Guix

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87il4kjagi.fsf@yoga.mail-host-address-is-not-set \
    --to=rustand.lars@gmail.com \
    --cc=68059@debbugs.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.