Package Details: luxmark 4.0alpha1-9

Git Clone URL: https://aur.archlinux.org/luxmark.git (read-only, click to copy)
Package Base: luxmark
Description: OpenCL benchmark tool
Upstream URL: https://github.com/LuxCoreRender/LuxMark
Licenses: GPL3
Submitter: Barthalion
Maintainer: DarkShadow44
Last Packager: DarkShadow44
Votes: 5
Popularity: 0.000000
First Submitted: 2018-01-06 20:59 (UTC)
Last Updated: 2025-04-19 01:34 (UTC)

Dependencies (20)

Required by (0)

Sources (5)

Latest Comments

1 2 3 4 5 Next › Last »

43615 commented on 2025-04-19 18:52 (UTC)

Apparently luxcorerender-bin-2.6-1 doesn't provide those files. Tried to build luxcorerender-2:2.7.beta1-2, but it has the same CMake version issue (reported it).

DarkShadow44 commented on 2025-04-19 17:58 (UTC)

It works for me, I get

-- LuxRays include directory: /usr/include
-- LuxRays config include directory: /usr/include
-- LuxRays library directory: /usr/lib/libluxrays.a

Do you have the following files:

- /usr/lib/libluxrays.a
- /usr/include/luxrays/luxrays.h 
- /usr/include/luxrays/cfg.h

They should be provided by luxcorerender 2:2.7.beta1-2

If you have those files and this doesn't work, please share the complete build log. Are you using makepkg directly or some helper?

43615 commented on 2025-04-19 12:21 (UTC)

New problem:

CMake Error at cmake/Dependencies.cmake:171 (MESSAGE):
  LuxRays not found.
Call Stack (most recent call first):
  CMakeLists.txt:102 (include)


-- Configuring incomplete, errors occurred!
==> ERROR: A failure occurred in build().
    Aborting...

DarkShadow44 commented on 2025-04-19 01:34 (UTC)

Thanks, fixed

43615 commented on 2025-04-18 20:19 (UTC)

Fails to build:

==> Starting build()...
-- CMAKE VERSION DETECTED 4.0.1
CMake Deprecation Warning at CMakeLists.txt:31 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value.  Or, use the <min>...<max> syntax
  to tell CMake that the project requires at least <min> but has been updated
  to work with policies introduced by <max> or earlier.


CMake Error at CMakeLists.txt:32 (cmake_policy):
  Compatibility with CMake < 3.5 has been removed from CMake.

  Update the VERSION argument <min> value.  Or, use the <min>...<max> syntax
  to tell CMake that the project requires at least <min> but has been updated
  to work with policies introduced by <max> or earlier.

  Or, add -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to try configuring anyway.


-- Configuring incomplete, errors occurred!
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'luxmark-4.0alpha1-8':

MarsSeed commented on 2023-07-23 20:01 (UTC)

Doesn't work:

$ luxmark
luxmark: error while loading shared libraries: libopenvdb.so.10.0: cannot open shared object file: No such file or directory

Installing openvdb results in a different error:

$ luxmark
luxmark: error while loading shared libraries: libfmt.so.9: cannot open shared object file: No such file or directory

Installing fmt and executing luxmark then results in the GUI appearing briefly, and doing the one-time compilation of the 'device kernel'; then it crashes with segmentation fault and dumps core.

Happens both when forcing NVIDIA GPU (proprietary driver) as well as letting it discover I have an Intel iGPU + a discrete NVIDIA GeForce.

DarkShadow44 commented on 2023-06-10 17:09 (UTC)

@MarsSeed Thank you for your effort! I'll push an update soon. This package already was supposed to link to python, but apparently libpython3.so and libpython3.11.so are not the same anymore... I'm used to those being symlinked and the same.

MarsSeed commented on 2023-06-10 13:40 (UTC)

Package also needs to depend on embree3, not the current embree (v4).

See cmake/Packages/FindEmbree.cmake.

MarsSeed commented on 2023-06-06 21:19 (UTC)

Apparently the latter is by design in boost.

See last comment of this bug:

https://bugs.archlinux.org/task/55798

It links to a source comment in boost, explaining the situation.

I am not sure why this is a new issue that had not occurred previously.

But apparently it is a problem in the luxmark linking configuration; the executable should be linked to the python binary.

MarsSeed commented on 2023-06-06 17:54 (UTC)

Hm, confirmed. The current boost-libs 1.81.0-6 libraries have undefined symbols:

$ ldd -r /usr/lib/libboost_numpy311.so.1.81.0
        linux-vdso.so.1 (0x00007ffdffc69000)
        libboost_python311.so.1.81.0 => /usr/lib/libboost_python311.so.1.81.0 (0x00007f26ba015000)
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007f26b9c00000)
        libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007f26b9ff0000)
        libc.so.6 => /usr/lib/libc.so.6 (0x00007f26b9a16000)
        libm.so.6 => /usr/lib/libm.so.6 (0x00007f26b9f03000)
        /usr/lib64/ld-linux-x86-64.so.2 (0x00007f26ba099000)
undefined symbol: PyExc_ValueError      (/usr/lib/libboost_python311.so.1.81.0)
undefined symbol: PyLong_AsLong (/usr/lib/libboost_python311.so.1.81.0)
undefined symbol: PyNumber_InPlaceFloorDivide   (/usr/lib/libboost_python311.so.1.81.0)
undefined symbol: PyBool_Type   (/usr/lib/libboost_python311.so.1.81.0)
undefined symbol: PyObject_GetAttr      (/usr/lib/libboost_python311.so.1.81.0)
undefined symbol: PyDict_GetItemString  (/usr/lib/libboost_python311.so.1.81.0)
undefined symbol: PyObject_Call (/usr/lib/libboost_python311.so.1.81.0)

[...] (output truncated)

1 2 3 4 5 Next › Last »