GNU bug report logs -
#68059
Mismatching defconfig options
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 68059 in the body.
You can then email your comments to 68059 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#68059
; Package
guix
.
(Wed, 27 Dec 2023 14:07:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Lars Rustand <rustand.lars <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Wed, 27 Dec 2023 14:07:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
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---
Information forwarded
to
bug-guix <at> gnu.org
:
bug#68059
; Package
guix
.
(Wed, 27 Dec 2023 16:56:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 68059 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hi Lars,
Lars Rustand <rustand.lars <at> 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
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#68059
; Package
guix
.
(Sat, 30 Dec 2023 11:56:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 68059 <at> debbugs.gnu.org (full text, mbox):
Josselin Poiret <dev <at> 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.
Reply sent
to
Josselin Poiret <dev <at> jpoiret.xyz>
:
You have taken responsibility.
(Fri, 12 Jan 2024 10:19:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Lars Rustand <rustand.lars <at> gmail.com>
:
bug acknowledged by developer.
(Fri, 12 Jan 2024 10:19:02 GMT)
Full text and
rfc822 format available.
Message #16 received at 68059-done <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hi Lars,
Lars Rustand <rustand.lars <at> gmail.com> writes:
> This issue can be closed.
You can close issues by replying to XXXX-done <at> debbugs.gnu.org instead of
XXXX@, as I'm doing here.
Best,
--
Josselin Poiret
[signature.asc (application/pgp-signature, inline)]
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Fri, 09 Feb 2024 12:24:13 GMT)
Full text and
rfc822 format available.
This bug report was last modified 1 year and 126 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.