update 1.5.1 http://www.luxrender.net/en_GB/community_news
Have you tested it ? Can you suggest a patch for the update ?
no
This version requires embree which is currently under review. https://bugzilla.redhat.com/show_bug.cgi?id=1364618 It also means x86 version is no more as well.
http://www.luxrender.net/forum/viewtopic.php?f=12&t=12885
Created attachment 1197027 [details] Update Luxrender.spec Hi kwizart, Could you investigate why the build failed at this line below: + /usr/bin/cmake -DCMAKE_C_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_CXX_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_Fortran_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON -DCMAKE_INSTALL_PREFIX:PATH=/usr -DINCLUDE_INSTALL_DIR:PATH=/usr/include -DLIB_INSTALL_DIR:PATH=/usr/lib64 -DSYSCONF_INSTALL_DIR:PATH=/etc -DSHARE_INSTALL_PREFIX:PATH=/usr/share -DLIB_SUFFIX=64 -DBUILD_SHARED_LIBS:BOOL=ON -DCMAKE_VERBOSE_MAKEFILE:BOOL=TRUE CMake Error: The source directory "/builddir/build/BUILD/luxrender-lux-b3f85cf7742f/luxrender-luxrays-61352e6aae3f/build" does not appear to contain CMakeLists.txt. Specify --help for usage, or press the help button on the CMake GUI. error: Bad exit status from /var/tmp/rpm-tmp.Lu9UZe (%build) Bad exit status from /var/tmp/rpm-tmp.Lu9UZe (%build) I include the spec file for information.
Assigned to f24 because the f23 failed to build due to version of python.
Here is the scratch build http://koji.fedoraproject.org/koji/taskinfo?taskID=15466715
/luxrender-luxrays-61352e6aae3f/build" does not appear to contain CMakeLists.txt. What does contains this directory ? does it even exists ? You probably need to update a snapshot of luxrays if not done already.
Created attachment 1200266 [details] Update Luxrender.spec I have no idea how that build part line failed as I haven't changed anything other than updating the luxray snapshot. Even removing the "mkdir -p build" line returned the same result leaving me baffled.
Created attachment 1207338 [details] Updated Luxrender.spec Cleaning the cmake line for building luxrays solved the problem. However, another issue appears with missing headers as seen on scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=15902022 The culprit is "#include <embree2/rtcore_bvh_builder.h>" which is not available on upstream embree currently 2.11. Possible solutions are: - Build an add-on for embree to include missing headers needed to properly build LuxRender i.e. extract them from the custom embree package from LuxRender developers. - Currently updated LuxRender to 1.4, the last version without embree dependency If someone has a proper suggestion, give a shot.
(In reply to Luya Tshimbalanga from comment #10) > Created attachment 1207338 [details] > Updated Luxrender.spec > > Cleaning the cmake line for building luxrays solved the problem. However, > another issue appears with missing headers as seen on scratch build: > http://koji.fedoraproject.org/koji/taskinfo?taskID=15902022 > > The culprit is "#include <embree2/rtcore_bvh_builder.h>" which is not > available on upstream embree currently 2.11. > If someone has a proper suggestion, give a shot. Is it possible to comment-out every functions that rely upon the custom embree from LuxRender ? How big is the change from the custom embree ?
Created attachment 1207641 [details] diff -ru embre-bvh_build and embree 2.11.0 There are about 38 files only for custom embree i.e. bvh_build after comparing with upstream embree. I don't know to comment them out.
(In reply to Luya Tshimbalanga from comment #12) > Created attachment 1207641 [details] > diff -ru embre-bvh_build and embree 2.11.0 > > There are about 38 files only for custom embree i.e. bvh_build after > comparing with upstream embree. I don't know to comment them out. Based on the diff -ru result, there are too many files to comment out meaning tracking all libraries made from custom embree inside the newest version of LuxRender. Possible solution is extract these custom libraries, package them separately and submit a suggestion to upstream LuxRender. It will be interesting to hear an alternative solution.
With the help from upstream, it turned out the tarball for lux was the wrong version. After getting the correct tarball, LuxRender successfully scratch built from Koji: http://koji.fedoraproject.org/koji/taskinfo?taskID=16118950 Version 1.6 is on the way and please don't forget to add karma.
LuxRender-1.6-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-2f01df1424
LuxRender-1.6-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-071eec4a0e
LuxRender-1.6-2.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-9148516d2d
LuxRender-1.6-2.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-8a1f343f48
LuxRender-1.6-2.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
LuxRender-1.6-2.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.