From: Maxime Devos <maximedevos@telenet.be>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>, 52411@debbugs.gnu.org
Subject: bug#52411: [core-updates-frozen] kmod-29 build fails, cross-compiled for i586-pc-gnu
Date: Fri, 10 Dec 2021 17:55:56 +0000 [thread overview]
Message-ID: <00552a0a31e0f72c0d0fb3251466fb245dd7fe42.camel@telenet.be> (raw)
In-Reply-To: <c59abe4993912bd7c2b5811953eae9aaf668b023.camel@telenet.be>
Maxime Devos schreef op vr 10-12-2021 om 17:48 [+0000]:
> Maxim Cournoyer schreef op vr 10-12-2021 om 07:55 [-0500]:
> > Hello Guix!
> >
> > I haven't been able to deploy core-updates-frozen on one of my
> > machine,
> > because it has the childhurd service which needs kmod-29 which
> > fails
> > building, like so:
>
> kmod is a linux-only thing, it's for doing things with linux kernel
> modules, so the childhurd service shouldn't be using kmod. Perhaps
> look
> at why kmod is being built in the first place?
I think I might have found the issue. The following commit made the
existence/absence 'kmod' input of pciutils depend on %current-
system/%current-target-system:
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=22ee7209797c023b95e22ced156df62cbff90184
but it forgot to keep in mind that nix systems != triplets.
Instead of %current-target-system, the 'current-target-nix-system'
from ‘https://issues.guix.gnu.org/49672#3’ needs to be used
(or the hurd-target? procedure).
Greetings,
Maxime.
next prev parent reply other threads:[~2021-12-10 17:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 12:55 bug#52411: [core-updates-frozen] kmod-29 build fails, cross-compiled for i586-pc-gnu Maxim Cournoyer
2021-12-10 17:48 ` Maxime Devos
2021-12-10 17:55 ` Maxime Devos [this message]
2021-12-16 19:02 ` Maxim Cournoyer
2021-12-18 4:11 ` Maxim Cournoyer
2021-12-18 4:42 ` Thiago Jung Bauermann via Bug reports for GNU Guix
2022-01-17 17:13 ` Maxim Cournoyer
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=00552a0a31e0f72c0d0fb3251466fb245dd7fe42.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=52411@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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.