From: Tobias Kortkamp <tobias.kortkamp@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 57430@debbugs.gnu.org, muradm <mail@muradm.net>,
Liliana Marie Prikler <liliana.prikler@gmail.com>
Subject: [bug#57430] [PATCH] gnu: wayland-protocols: Fix cross-compilation
Date: Sat, 27 Aug 2022 12:40:12 +0200 [thread overview]
Message-ID: <Ywn0jMXYtd0XA0aV@anubis> (raw)
In-Reply-To: <9733f5e2-ffc9-b81e-5806-2536c02246bd@telenet.be>
On Fri, Aug 26, 2022 at 08:58:51PM +0200, Maxime Devos wrote:
> Tobias, does unconditionally moving wayland from 'inputs' to 'native-inputs'
> (and unconditionally using pkg-config-for-build) work? Potential problem:
> lots of dependents according to "guix refresh -l", making it unconditional
> would need to be done on core-updates or staging.
You mean change the patch like this?
- (inputs
- (list wayland))
- (native-inputs (cons* pkg-config python
- (if (%current-target-system)
- (list pkg-config-for-build
- wayland) ; for wayland-scanner
- '())))
+ (native-inputs (list pkg-config pkg-config-for-build wayland python))
No, it doesn't work:
Run-time dependency wayland-client found: NO (tried pkgconfig)
../wayland-protocols-1.23/tests/meson.build:4:0: ERROR: Dependency "wayland-client" not found, tried pkgconfig
What would work is:
+ (arguments `(#:configure-flags (list "-Dtests=false")))
+ (native-inputs (list pkg-config-for-build wayland))
But this turns off the tests. Even then it still looks for
wayland-scanner for some reason.
next prev parent reply other threads:[~2022-08-27 10:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 10:14 [bug#57430] [PATCH] gnu: wayland-protocols: Fix cross-compilation Tobias Kortkamp
2022-08-26 15:04 ` Maxime Devos
2022-08-26 16:59 ` muradm
2022-08-26 18:58 ` Maxime Devos
2022-08-26 19:22 ` Liliana Marie Prikler
2022-08-26 20:34 ` Maxime Devos
2022-08-27 10:40 ` Tobias Kortkamp [this message]
2022-08-27 11:02 ` Maxime Devos
2022-08-30 7:18 ` bug#57430: " Mathieu Othacehe
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Ywn0jMXYtd0XA0aV@anubis \
--to=tobias.kortkamp@gmail.com \
--cc=57430@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=mail@muradm.net \
--cc=maximedevos@telenet.be \
/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 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).