Package Details: mitsuba-git 0.6.0.r2173.10af06f3-1

Git Clone URL: https://aur.archlinux.org/mitsuba-git.git (read-only, click to copy)
Package Base: mitsuba-git
Description: Mitsuba physically based renderer.
Upstream URL: http://mitsuba-renderer.org/
Keywords: 3d metropolis-light-transport pathrace renderer
Licenses: GPL3
Conflicts: mitsuba, mitsuba-hg
Provides: mitsuba
Submitter: bartus
Maintainer: bartus (maz-1)
Last Packager: bartus
Votes: 3
Popularity: 0.000000
First Submitted: 2016-11-28 20:18 (UTC)
Last Updated: 2024-01-16 14:56 (UTC)

Pinned Comments

bartus commented on 2019-04-10 11:42 (UTC) (edited on 2024-01-16 10:06 (UTC) by bartus)

Please report issues and patches to mitsuba-git->github.com

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

frankspace commented on 2019-11-15 13:12 (UTC)

Compilation appears to succeed, but installation fails:

.
.
.
Install file: "build/release/integrators/volpath.so" as "dist/plugins/volpath.so"
Install file: "build/release/integrators/volpath_simple.so" as "dist/plugins/volpath_simple.so"
Install file: "build/release/integrators/vpl.so" as "dist/plugins/vpl.so"
Install file: "build/release/bsdfs/ward.so" as "dist/plugins/ward.so"
Install file: "build/release/textures/wireframe.so" as "dist/plugins/wireframe.so"
Install file: "build/release/libpython/mitsuba_python2.7.so" as "dist/python/2.7/mitsuba.so"
scons: done building targets.
==> Entering fakeroot environment...
==> Starting package()...
install: cannot stat 'dist/python/3.8/mitsuba.so': No such file or directory
==> ERROR: A failure occurred in package().
    Aborting...

I tried updating the python patch to include version 3.8, but that didn't help.

bartus commented on 2019-04-10 11:42 (UTC) (edited on 2024-01-16 10:06 (UTC) by bartus)

Please report issues and patches to mitsuba-git->github.com

bartus commented on 2018-02-22 10:56 (UTC) (edited on 2018-02-22 10:56 (UTC) by bartus)

Now, it looks pretty obvious, thanks @dTal!

dTal commented on 2018-02-22 01:10 (UTC) (edited on 2018-02-22 01:14 (UTC) by dTal)

It seems that the file in question compiles fine without the C++11 flag. Adding this second sed line to the PKGBUILD to remove the flag only for that file fixes the problem for me:

sed -i "/irawanEnv =/airawanEnv.RemoveFlags(['-std=gnu\+\+11'])" src/bsdfs/SConscript

(Note I modified the flag to -std=gnu++11 to match your updated PKGBUILD)

EDIT: The comment box garbles the backslashes. There should be three before each '+' character.

bartus commented on 2018-02-20 11:56 (UTC) (edited on 2018-02-20 12:09 (UTC) by bartus)

@dTal Notice the issue a while ago now. Sadly my boost-foo is quite lacking, and sourly not in any way suitable for reworking Jakob's code. Check this comment in SConsScript ;)

# The Irawan-Marschner plugin uses a Boost::Spirit parser, which makes it
# pretty heavy stuff to compile. Go easy on the compiler flags:

Will try to suppress irawan bsdf all together, let's see if that works.

Update: Done, check if that's working for you?

dTal commented on 2018-02-20 00:56 (UTC) (edited on 2018-02-20 00:57 (UTC) by dTal)

The build erroneously complains that xercesc is not installed - in fact, checking config.log shows that it does, but that it throws an error very like this one: https://bugs.gentoo.org/show_bug.cgi?id=572626

Adding:

sed -i -e 's:gnu2:gnu2\x27, \x27-std=c++11:g' config.py

to the PKGBUILD, allows the build to continue.

Unfortunately, build still fails, much later, with:

In file included from src/bsdfs/irawan.cpp:33:0:src/bsdfs/irawan.h: In constructor ‘mitsuba::YarnGrammar<iterator>::YarnGrammar(const mitsuba::Properties&)’:src/bsdfs/irawan.h:314:84: error: no matching function for call to ‘bind(<unresolved function="" overloaded="" type="">, const type, const _1_type&)’</unresolved></iterator>

bartus commented on 2016-11-28 20:28 (UTC) (edited on 2016-11-30 07:57 (UTC) by bartus)

I notice a strange 'quirk', ( no idea where it originate from ) When rebuilding package you can end up with truncated archive producing empty libmistuba-renderer.so file upon installation. Which in turns prevent successful rebuild of package. Steps to resolve the issue involve removing mitsuba-git prior to reinitialize build procedure. Maybe it's specific case to my system but be aware.

« First ‹ Previous 1 2 3 Next › Last »