all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Pavel Shlyak <p.shlyak@pantherx.org>, 56263@debbugs.gnu.org
Subject: bug#56263: set-paths phase throws match-error "match" "no matching pattern" while cross-compiling a kernel module
Date: Wed, 10 Aug 2022 20:02:07 +0200	[thread overview]
Message-ID: <b9021b87-ca72-d86e-abbd-ddd840fa7a64@telenet.be> (raw)
In-Reply-To: <7DAC1F06-8B35-4677-B072-9E65FEF8EC59@pantherx.org>


[-- Attachment #1.1.1: Type: text/plain, Size: 1577 bytes --]


On 27-06-2022 20:05, Pavel Shlyak wrote:
> I don’t know the reason it happens. Maybe it’s somehow related to file-append hack that is used to set driver location in the repo. The other problem can be about
> inputs or native-inputs being empty. Anyway, package definition looks fine to me and I suppose there’s a problem with set-paths phase.
> Package definition:
> https://git.pantherx.org/development/hardware/raspberry/-/blob/c9260f1720f63c409ef3ce88cefa677a21eb9e0b/reterminal.scm
> Package ltr30x-linux-module builds successfully here with aarch64 host and it fails if I cross-compile it with x86_64 host
> Error log here:
> https://gist.github.com/shlyakpavel/b8b53e9bb4392cce1bba3c77c6d35d58

linux-module-build-cross quotes stuff:

           (define %build-host-inputs
             '#+(input-tuples->gexp build-inputs))

but 'input-tuples->gexp' already returns something quoted, so its quoted 
twice.

Try removing the 'quote' (i.e., ').

No relation to file-append as far as I can tell.


In rpi-kernel.scm, you are copying stuff from linux.scm without 
preserving copyright lines or the license header and the GPL license 
text is also removed; please respect the GPL license.

In the README, you are writing GUIX, but the standard capitalisation is 
Guix (sometimes guix, but never GUIX outside things like environment 
variable names).

License headers are missing from teterminal.scm, I recommend being 
explicit (gpl3 is kind of implied, but do you mean gpl3-only or gpl3+?)

Greetings,
Maxime.


[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

      parent reply	other threads:[~2022-08-10 18:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27 18:05 bug#56263: set-paths phase throws match-error "match" "no matching pattern" while cross-compiling a kernel module Pavel Shlyak
2022-06-27 18:10 ` bug#56263: Another reproducer Pavel Shlyak
2022-08-10 17:00 ` bug#56263: set-paths phase throws match-error "match" "no matching pattern" while cross-compiling a kernel module Pavel Shlyak
2022-08-10 17:45 ` Maxime Devos
2022-08-10 18:02 ` Maxime Devos [this message]

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=b9021b87-ca72-d86e-abbd-ddd840fa7a64@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=56263@debbugs.gnu.org \
    --cc=p.shlyak@pantherx.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.