Package Details: kvazaar 1.2.0-6

Git Clone URL: (read-only)
Package Base: kvazaar
Description: An open-source HEVC encoder
Upstream URL:
Keywords: codec encoder h.265 h265 HEVC kvazaar libkvazaar libx265 ultravideo video x265
Licenses: LGPL
Submitter: dbermond
Maintainer: dbermond
Last Packager: dbermond
Votes: 34
Popularity: 0.285880
First Submitted: 2015-12-27 19:34
Last Updated: 2018-10-26 19:16

Latest Comments

1 2 Next › Last »

fitu996 commented on 2018-02-26 08:56

This package need a rebuild. Otherwise ffmpeg-full cannot build.

Here is the output when I build ffmpeg-full:

==> Starting build()...
  -> Running ffmpeg configure script. Please wait...
ERROR: kvazaar >= 0.8.1 not found using pkg-config

If you think configure made a mistake, make sure you are using the latest
version from Git.  If the latest version fails, report the problem to the mailing list or IRC #ffmpeg on
Include the log file "ffbuild/config.log" produced by configure as this will help
solve the problem.

dbermond commented on 2018-02-01 14:14

@Karmadon @friday13 This is a compile issue with the newly released crypto++ v6.0.0. I have temporarily disabled crypto++ support until there is an upstream fix. Package is building fine now.

@Karmadon Yes, it was me that created upstream issue #184 on github :)

friday13 commented on 2018-02-01 13:37

make[2]: *** [Makefile:1473: extras/crypto.lo] Error 1 make[2]: Leaving directory '/tmp/yaourt-tmp-friday13/aur-kvazaar/src/kvazaar-1.2.0/src' make[1]: *** [Makefile:524: all-recursive] Error 1 make[1]: Leaving directory '/tmp/yaourt-tmp-friday13/aur-kvazaar/src/kvazaar-1.2.0' make: *** [Makefile:394: all] Error 2

Karmadon commented on 2018-02-01 12:22

Oh it seems to me someone already created a bug report

Best regards

Karmadon commented on 2018-02-01 12:20

Hello! I get these errors during package building:

extras/crypto.cpp:19:3: error: ‘byte’ does not name a type byte key[CryptoPP::AES::DEFAULT_KEYLENGTH]; ^~~~ CC strategies/avx2/libavx2_la-quant-avx2.lo extras/crypto.cpp:20:3: error: ‘byte’ does not name a type byte iv[CryptoPP::AES::BLOCKSIZE]; ^~~~ extras/crypto.cpp:21:3: error: ‘byte’ does not name a type byte out_stream_counter[CryptoPP::AES::BLOCKSIZE]; ^~~~ extras/crypto.cpp:22:3: error: ‘byte’ does not name a type byte counter[CryptoPP::AES::BLOCKSIZE]; ^~~~

What can I do to compile the package?

Best regards, Roman

dbermond commented on 2017-10-08 14:06

Hi. Thank you for the interest in this package.
That's the normal and expected behavior of the Kvazaar upstream source. In order to obtain the program version (for printing in the binary executable), it will check if it's being built from a git repository source or from a tarball source. You can view it on these links:

If it's being built from a git repository source, the kvazaar binary will output a version (with $ kvazaar --version) in the format 'v1.1.0-156-g957b685 2017-09-25' to reflect the development version. If it's being built from a tarball source (our case here), the kvazaar binary will output a version in the format 'v1.1.0' to reflect the stable version.

Since the upstream source does not ship with a pre-built configure script, we need to generate it by running This script is the responsible for showing these git messages if you don't have git installed or if the directory is not a git repository source. That's because it not only generates the configure script, but it also initializes the git submodules, as you can see here:

Nothing4You commented on 2017-10-08 01:35

Currently when building this if you don't have git installed you will get this:

==> Starting prepare()...
./ line 3: git: command not found
./ line 4: git: command not found
[continuing normally]

If you do have git installed you'll get

==> Starting prepare()...
fatal: Not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
fatal: Not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
[continuing normally]

Is that intended?

dbermond commented on 2017-01-09 17:44

I really forgot to add a 'make' command to build(). Fixed in 1.0.0-5.
Thanks for noting this.

dreieck commented on 2017-01-02 14:35

Please move the compilatiopn from the package()-function to the build()-function! package() is for copying the files in place, build() is for make.

(Split it up: Do a "make" in build() and a "make DESTDIR=..." in package())

dbermond commented on 2016-07-01 17:32

'autoconf' and 'automake' are part of the 'base-devel' group and thus should already be installed.