Package Base Details: libjxl-git

Git Clone URL: https://aur.archlinux.org/libjxl-git.git (read-only, click to copy)
Keywords: jpeg-xl
Submitter: dbermond
Maintainer: dbermond
Last Packager: dbermond
Votes: 14
Popularity: 0.000050
First Submitted: 2021-06-02 18:30 (UTC)
Last Updated: 2024-03-01 15:40 (UTC)

Latest Comments

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

dbermond commented on 2022-08-02 01:08 (UTC)

@frankenstein20 I've just checked, and the package is building fine for me. Looking at the error that you are having, it seems that the java bindings is not being built during build(). This can happen if the build system does not recognize your installed java. I'm using jdk-openjdk from the official repositories (currently at version 18.0.2.u9), and the package builds fine with it. Also, you are using an AUR helper, and this is not supported. Use makepkg.

@markg85 Good to know that you could fulfill your needs.

frankenstein20 commented on 2022-08-01 11:54 (UTC)

Hi all

I get an error after

==> Beginne package_libjxl-git()...
I get
mv: der Aufruf von stat für '/home/ftornack/.cache/pikaur/build/libjxl-git/pkg/libjxl-git/usr/share/java/org.jpeg.jpegxl.jar' ist nicht möglich: Datei oder Verzeichnis nicht gefunden

Sorry for the german... it is a file not found error

markg85 commented on 2022-07-26 14:16 (UTC) (edited on 2022-07-26 14:22 (UTC) by markg85)

@dbermond oke.. :)

I tried to compile it now using makepkg.. I'm getting a boat load of errors:

/usr/include/hwy/targets.h: In function ‘std::vector<unsigned int> hwy::SupportedAndGeneratedTargets()’:
<command-line>: error: ‘HWY_SVE_256’ was not declared in this scope; did you mean ‘HWY_SVE2’?
<command-line>: error: ‘HWY_SVE2_128’ was not declared in this scope; did you mean ‘HWY_SVE2’?
In file included from /usr/include/hwy/highway.h:24,
                 from /home/mark/pkgbuilds/libjxl-git/src/libjxl/lib/jxl/convolve-inl.h:13,
                 from /home/mark/pkgbuilds/libjxl-git/src/libjxl/lib/jxl/convolve_slow.cc:8:
/usr/include/hwy/targets.h: In member function ‘size_t hwy::ChosenTarget::GetIndex() const’:
<command-line>: error: ‘HWY_SVE_256’ was not declared in this scope; did you mean ‘HWY_SVE2’?
In file included from /usr/include/hwy/highway.h:24,
                 from /home/mark/pkgbuilds/libjxl-git/src/libjxl/lib/jxl/color_management.cc:23,
                 from /usr/include/hwy/foreach_target.h:80,
                 from /home/mark/pkgbuilds/libjxl-git/src/libjxl/lib/jxl/color_management.cc:22:

I didn't change the PKGBUILD so am still using whatever this package claims it needs.

^^ never mind the above. While it is an issue, i don't actually need the manually build one. I started using it when there was no libjxl package in the arch repos yet and wanted to play with the cjxl command. libjxl now seems to be in the arch packages so i'm using that instead. Works just fine for my case.

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.