Github messages for voidlinux
 help / color / mirror / Atom feed
From: Konata390 <Konata390@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: krfb: add pipewire dependency
Date: Thu, 17 Feb 2022 12:30:19 +0100	[thread overview]
Message-ID: <20220217113019.uLrRaUFed2peBIpTYzz8jmh-6vvlYvzcGzx_ceIBfsk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35660@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 912 bytes --]

New comment by Konata390 on void-packages repository

https://github.com/void-linux/void-packages/pull/35660#issuecomment-1042853331

Comment:
I don't know what I did, but I can't reproduce my earlier issue anymore. Now I always get this error (with or without the added `configure_args`):

`[1/18] Generating wayland-zkde-screencast-unstable-v1-client-protocol.h
FAILED: framebuffers/pipewire/wayland-zkde-screencast-unstable-v1-client-protocol.h /builddir/krfb-21.12.1/build/framebuffers/pipewire/wayland-zkde-screencast-unstable-v1-client-protocol.h 
cd /builddir/krfb-21.12.1/build/framebuffers/pipewire && /usr/bin/wayland-scanner client-header /usr/armv7l-linux-gnueabihf/usr/share/plasma-wayland-protocols/screencast.xml /builddir/krfb-21.12.1/build/framebuffers/pipewire/wayland-zkde-screencast-unstable-v1-client-protocol.h
/bin/sh: line 1: /usr/bin/wayland-scanner: No such file or directory
`


  parent reply	other threads:[~2022-02-17 11:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17  7:01 [PR PATCH] " Konata390
2022-02-17  9:54 ` Konata390
2022-02-17 10:15 ` Johnnynator
2022-02-17 11:30 ` Konata390 [this message]
2022-02-17 11:38 ` Johnnynator
2022-02-17 11:42 ` [PR PATCH] [Updated] " Konata390
2022-02-17 14:22 ` Konata390
2022-02-17 18:27 ` Johnnynator
2022-02-18 20:31 ` [PR PATCH] [Closed]: " Johnnynator

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=20220217113019.uLrRaUFed2peBIpTYzz8jmh-6vvlYvzcGzx_ceIBfsk@z \
    --to=konata390@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).