From: kawaiiamber <kawaiiamber@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: QtPBFImagePlugin-2.3
Date: Mon, 01 Feb 2021 12:13:14 +0100 [thread overview]
Message-ID: <20210201111314.B-Rcvw9kbG3Ros4zxlO2YLEJ4WmJQWfGX6OdkfRYq-k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28330@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]
New comment by kawaiiamber on void-packages repository
https://github.com/void-linux/void-packages/pull/28330#issuecomment-770778218
Comment:
```
protoc --cpp_out=protobuf --proto_path=protobuf protobuf/vector_tile.proto
make: protoc: No such file or directory
make: *** [Makefile:432: protobuf/vector_tile.pb.h] Error 127
=> ERROR: QtPBFImagePlugin-2.3_1: do_build: '${make_cmd} ${makejobs} ${make_build_args} ${make_build_target} CC="$CC" CXX="$CXX" LINK="$CXX"' exited with 2
=> ERROR: in do_build() at common/build-style/qmake.sh:136
Error: Process completed with exit code 1.
```
Their `Makefile` is trying to use a `protoc` command. Use `xlocate` to find out where it's at.
```sh
[amber@otaku ~]$ xlocate /usr/bin/protoc
kio-5.78.0_1 /usr/bin/protocoltojson
protobuf-c-1.3.3_5 /usr/bin/protoc-c -> /usr/bin/protoc-gen-c
protobuf-c-1.3.3_5 /usr/bin/protoc-gen-c
protobuf-vala-0.1.0_3 /usr/bin/protoc-gen-vala
protobuf18-3.7.1_3 /usr/bin/protoc
protobuf23-3.12.4_1 /usr/bin/protoc
protobuf24-3.13.0.1_1 /usr/bin/protoc
protobuf25-3.14.0_1 /usr/bin/protoc
```
Looks like you might need the `protobuf` package.
next prev parent reply other threads:[~2021-02-01 11:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 14:10 [PR PATCH] " Sarkasper
2021-02-01 11:13 ` kawaiiamber [this message]
2021-02-01 11:18 ` kawaiiamber
2022-05-03 2:13 ` github-actions
2022-05-17 2:14 ` [PR PATCH] [Closed]: " github-actions
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=20210201111314.B-Rcvw9kbG3Ros4zxlO2YLEJ4WmJQWfGX6OdkfRYq-k@z \
--to=kawaiiamber@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).