unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
* bug#68059: Mismatching defconfig options
@ 2023-12-27  8:35 Lars Rustand
  2023-12-27 16:55 ` Josselin Poiret via Bug reports for GNU Guix
  0 siblings, 1 reply; 4+ messages in thread
From: Lars Rustand @ 2023-12-27  8:35 UTC (permalink / raw)
  To: 68059


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---




^ permalink raw reply	[flat|nested] 4+ messages in thread

* bug#68059: Mismatching defconfig options
  2023-12-27  8:35 bug#68059: Mismatching defconfig options Lars Rustand
@ 2023-12-27 16:55 ` Josselin Poiret via Bug reports for GNU Guix
  2023-12-30 10:39   ` Lars Rustand
  0 siblings, 1 reply; 4+ messages in thread
From: Josselin Poiret via Bug reports for GNU Guix @ 2023-12-27 16:55 UTC (permalink / raw)
  To: Lars Rustand, 68059

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

Hi Lars,

Lars Rustand <rustand.lars@gmail.com> writes:

> 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.

Could you post the exact error that you get?

> 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?

Guix doesn't modify the defconfig you give it, it just moves it to
guix_defconfig.  However, it then tries to verify that the defconfig was
properly applied, which is completely Guix-specific and might be the
thing that doesn't work properly.

> 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---

Best,
-- 
Josselin Poiret

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* bug#68059: Mismatching defconfig options
  2023-12-27 16:55 ` 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
  0 siblings, 1 reply; 4+ messages in thread
From: Lars Rustand @ 2023-12-30 10:39 UTC (permalink / raw)
  To: 68059; +Cc: Josselin Poiret


Josselin Poiret <dev@jpoiret.xyz> writes:

> Guix doesn't modify the defconfig you give it, it just moves it to
> guix_defconfig.  However, it then tries to verify that the defconfig was
> properly applied, which is completely Guix-specific and might be the
> thing that doesn't work properly.

Thanks, this must be it. I guess there is an option in the config that
does not apply correctly, but since there is no verification in the
normal build process it only causes a problem in Guix. Deleting the
problematic line in the defconfig made it build correctly, so I guess
this is not a problem in Guix, but in the defconfig I was trying to use.

This issue can be closed.




^ permalink raw reply	[flat|nested] 4+ messages in thread

* bug#68059: Mismatching defconfig options
  2023-12-30 10:39   ` Lars Rustand
@ 2024-01-12 10:17     ` Josselin Poiret via Bug reports for GNU Guix
  0 siblings, 0 replies; 4+ messages in thread
From: Josselin Poiret via Bug reports for GNU Guix @ 2024-01-12 10:17 UTC (permalink / raw)
  To: Lars Rustand, 68059-done

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

Hi Lars,

Lars Rustand <rustand.lars@gmail.com> writes:

> This issue can be closed.

You can close issues by replying to XXXX-done@debbugs.gnu.org instead of
XXXX@, as I'm doing here.

Best,
-- 
Josselin Poiret

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2024-01-12 10:19 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-12-27  8:35 bug#68059: Mismatching defconfig options Lars Rustand
2023-12-27 16:55 ` 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

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).