From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: CopyQ: update to 4.1.0.
Date: Mon, 17 May 2021 17:01:00 +0200 [thread overview]
Message-ID: <20210517150100.Ktc0S0oy0wGIumiFTyn-hwcT8zGRixZf6PRyrKQNwvc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30918@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1491 bytes --]
New comment by Johnnynator on void-packages repository
https://github.com/void-linux/void-packages/pull/30918#issuecomment-842396767
Comment:
> I am not sure cross-compilation is possible :(
> QtWaylandScanner_EXECUTABLE is in qt5-wayland-devel. If that is placed in the hostmakedepends array, the configuration step works, but build fails because there is an arch mishmatch when wayland-scanner tries to compile a file:
>
> ```
> 105/280] Automatic MOC for target systemclipboard
> [106/280] Generating wayland-wlr-data-control-unstable-v1-client-protocol.h
> FAILED: src/platform/x11/systemclipboard/wayland-wlr-data-control-unstable-v1-client-protocol.h
> cd /builddir/CopyQ-4.1.0/build/src/platform/x11/systemclipboard && /usr/aarch64-linux-musl/usr/bin/wayland-scanner client-header /builddir/CopyQ-4.1.0/src/platform/x11/systemclipboard/wlr-data-control-unstable-v1.xml /builddir/CopyQ-4.1.0/build/src/platform/x11/systemclipboard/wayland-wlr-data-control-unstable-v1-client-protocol.h
> /bin/sh: line 1: /usr/aarch64-linux-musl/usr/bin/wayland-scanner: cannot execute binary file: Exec format error
> ninja: build stopped: subcommand failed.
> => ERROR: CopyQ-4.1.0_1: do_build: '${make_cmd} ${makejobs} ${make_build_args} ${make_build_target}' exited with 1
> => ERROR: in do_build() at common/build-style/cmake.sh:82
> ```
You also need `wayland-devel` in hostmakepends. (and maybe also `-DWaylandScanner_EXECUTABLE=/usr/bin/wayland-scanner` in configure_args)
next prev parent reply other threads:[~2021-05-17 15:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 20:44 [PR PATCH] " mobinmob
2021-05-17 3:23 ` ericonr
2021-05-17 14:45 ` mobinmob
2021-05-17 14:46 ` mobinmob
2021-05-17 15:00 ` q66
2021-05-17 15:01 ` Johnnynator [this message]
2021-05-17 21:02 ` [PR PATCH] [Updated] " mobinmob
2021-05-21 5:08 ` [PR PATCH] [Closed]: " ericonr
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=20210517150100.Ktc0S0oy0wGIumiFTyn-hwcT8zGRixZf6PRyrKQNwvc@z \
--to=johnnynator@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).