Package Details: libjxl-git 0.11.0.r55.g8da7c884-1

Git Clone URL: https://aur.archlinux.org/libjxl-git.git (read-only, click to copy)
Package Base: libjxl-git
Description: JPEG XL image format reference implementation (git version)
Upstream URL: https://jpeg.org/jpegxl/
Keywords: jpeg-xl
Licenses: BSD-3-Clause
Conflicts: libjpeg-xl-git, libjxl
Provides: libjpeg-xl-git, libjxl, libjxl.so, libjxl_threads.so
Replaces: libjpeg-xl-git
Submitter: dbermond
Maintainer: dbermond
Last Packager: dbermond
Votes: 15
Popularity: 0.69
First Submitted: 2021-06-02 18:30 (UTC)
Last Updated: 2024-11-09 22:47 (UTC)

Dependencies (26)

Required by (85)

Sources (11)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 13 Next › Last »

dbermond commented on 2022-07-24 02:06 (UTC)

@markg85

1) No, sorry. Contrary to what you said, the check() function is very important. Quoting the Arch Wiki: "It is highly recommended to have check() as it helps to make sure software has been built correctly and works fine with its dependencies". Being such, check() should be used whenever possible. If you don't want to run the tests, you can use the makepkg '--nocheck' option for convenience, but this is not recommended.

2) No, sorry. 'java-runtime' is already an optional dependency, so it can be lightweight at runtime. 'java-environment' is needed only at build time, and can be uninstalled after it. The package is building fine for me using 'jdk-openjdk' from the official repositories (currently at version 18.0.2). A segfault when compiling does not seem to be a packaging issue, and, at a first glance, it looks like to be an issue with your system. As far as I'm concerned, you're not supposed to get a segfault when compiling software. You are using an AUR helper, and this is not supported. Make sure that you are not using AUR helpers, and that you are on Arch Linux.

markg85 commented on 2022-07-24 01:39 (UTC) (edited on 2022-07-24 01:39 (UTC) by markg85)

Hi,

A couple of questions. 1). Could you disable the tests in compilation. They take quite some time to run and it doesn't seem important for me to have these just on Arch. Tests are important for those that develop the library itself.

2). Could the java dependency be removed, please? It adds a ton of extra packages and - even more important - it fails for me with the following:

make[1]: *** [CMakeFiles/Makefile2:4153: tools/box/CMakeFiles/box.dir/all] Segmentation fault (core dumped)
make[1]: *** Waiting for unfinished jobs....
[ 63%] Built target jxlinfo
[ 63%] Built target djxl
[ 64%] Built target cjxl
[ 65%] Built target cjpeg_hdr
make[1]: Leaving directory '/home/mark/.cache/yay/libjxl-git/src/build'
make: *** [Makefile:146: all] Error 2
make: Leaving directory '/home/mark/.cache/yay/libjxl-git/src/build'
==> ERROR: A failure occurred in package_libjxl-git().
    Aborting...
 -> error making: libjxl-git

dbermond commented on 2022-04-25 17:52 (UTC)

@JDAturbo That's because upstream does not fix their git repository to give the correct version with the git describe command. I always left this way in hope they can someday properly update this, but it's really taking too long.

JDAturbo commented on 2022-04-25 17:47 (UTC)

I believe the pkgver is wrong. The version on main branch is 0.7.0: https://github.com/libjxl/libjxl/blob/main/lib/CMakeLists.txt

andrius4669 commented on 2022-01-10 20:16 (UTC)

https://github.com/google/highway/issues/497 has been fixed and now it instead fails on https://github.com/libjxl/libjxl/issues/1080

andrius4669 commented on 2022-01-09 21:59 (UTC)

that wouldn't be an issue if -DJPEGXL_FORCE_SYSTEM_HWY:BOOL='true' wasn't set. why is that submodule, at known working commit, is even being cloned if broken one is being depended upon instead?

anyway I've reported https://github.com/google/highway/issues/497, we'll see how that goes. but consider taking off -DJPEGXL_FORCE_SYSTEM_HWY:BOOL='true', while i kinda know reasons not to, it's got bigger chances to break stuff with untested hwy commits.

dbermond commented on 2022-01-06 18:48 (UTC)

@yaron This is an upstream issue, probably on highway. It looks like a commit that was made today on upstream highway broke the libjxl build.

yaron commented on 2022-01-06 14:28 (UTC)

@dbermond there seem to be an error while compiling this version:

In file included from /usr/include/hwy/tests/test_util-inl.h:22:
/usr/include/hwy/tests/test_util.h:26:10: fatal error: 'hwy/tests/include_farm_sve.h' file not found
#include "hwy/tests/include_farm_sve.h"
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.

dbermond commented on 2022-01-03 02:09 (UTC)

@Yatha package updated to match the latest upstream changes.

Yatha commented on 2022-01-02 19:53 (UTC)

This package required "gflags" package. Otherwise " libgflags not found " error occured

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 13 Next › Last »