Package Details: mitsuba-git 0.6.0.r2170.450a2b8a-1

Git Clone URL: https://aur.archlinux.org/mitsuba-git.git (read-only)
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
Last Updated: 2018-09-15 13:02

Pinned Comments

bartus commented on 2019-04-10 11:42

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

Latest Comments

bartus commented on 2019-04-10 11:42

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

bartus commented on 2018-02-22 10:56

Now, it looks pretty obvious, thanks @dTal!

dTal commented on 2018-02-22 01:10

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

@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

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

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.

afichet commented on 2016-09-16 11:23

Thanks bartus!
Just need to modify checksum in your fix for patches and works like a charm.

bartus commented on 2016-08-11 20:38

Mitsuba relies upon GLEWmx witch was discontinued as of glew 2.0.0.

A 'work around' build procedure requires:
1. Build glew-1.13.0 (non-conflicting, can be instlled alongside glew 2.0.0)
> PKGBUILD: http://pastebin.com/T6rLhsEQ
2. Build collada-dom-mitsuba (working PKGBUILD and patch)
> PKGBUILD: http://pastebin.com/8jYiUwRG
> 0001-fix-return-type-thanks-to-22.patch : http://pastebin.com/c7Q8ZcB1
3. Finaly build mitsuba with altered PKGBUILD and python3.5.patch
> PKGBUILD: http://pastebin.com/DXcFiE7S
> python3.5.patch : http://pastebin.com/6EU7zpu0
All tested in clean chroot build.