Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - ospray

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: ospray 1.1.2-5

Git Clone URL: https://aur-dev.archlinux.org/ospray.git (read-only)
Package Base: ospray
Description: A Ray Tracing Based Rendering Engine for High-Fidelity Visualization
Upstream URL: http://www.ospray.org/
Licenses: Apache
Submitter: gucong
Maintainer: gucong
Last Packager: gucong
Votes: 5
Popularity: 1.756200
First Submitted: 2016-08-11 00:08
Last Updated: 2017-01-24 21:50

Latest Comments

1 2 Next › Last »

gucong commented on 2017-01-24 21:52

@kosh Looks like they repackaged the source tarball. It should work now.

kosh commented on 2017-01-24 20:16

Now the package fails the validity check. If I skip it, it then complains that there is no folder "src/OSPRay-1.1.2". If I create it, it complains that there is no "CMakeLists.txt" in this folder and so on =) it seems that package is broken

gdonval commented on 2016-12-17 20:29

I had the same problem which was caused by the CFLAGS I was using: for whatever reason, providing "-march=native" is breaking everything (and I really don't see why as this provides optimisation opportunities, it does not force anything).

Hell-G commented on 2016-12-14 17:02

Thanks for your reply. According to /proc/cpuinfo:
model name : Intel(R) Core(TM) i5-3427U CPU @ 1.80GHz
flags: ... sse4_2 ...

gucong commented on 2016-12-14 16:41

@Hell-G What is the model of your CPU? According to https://github.com/ospray/OSPRay/issues/110 , the minimum requirement is SSE4.2 support.

Hell-G commented on 2016-12-14 10:26

Hi guys,
I am not able to build the package. I get a lot of undefined references to embree stuff and then the compilation aborts. I have embree-isa 2.12.0-1 installed. Any hints? Thanks!

/usr/lib64/cmake/embree-2.12.0/../../libembree.so.2.12.0: undefined reference to `embree::sse42::BVH4Subdivpatch1EagerIntersector1'
/usr/lib64/cmake/embree-2.12.0/../../libembree.so.2.12.0: undefined reference to `embree::BVHN<4>::postBuild(double)'
/usr/lib64/cmake/embree-2.12.0/../../libembree.so.2.12.0: undefined reference to `embree::sse42::BVH4Triangle4vIntersector1Pluecker'
/usr/lib64/cmake/embree-2.12.0/../../libembree.so.2.12.0: undefined reference to `embree::sse42::BVH4Subdivpatch1CachedIntersector4'
/usr/lib64/cmake/embree-2.12.0/../../libembree.so.2.12.0: undefined reference to `embree::sse42::BVH4Quad4vIntersector4HybridMoellerNoFilter'
/usr/lib64/cmake/embree-2.12.0/../../libembree.so.2.12.0: undefined reference to `embree::sse42::BVH4Triangle4vMBIntersector1Moeller'
collect2: error: ld returned 1 exit status
make[2]: *** [builddir/ospray/intel64/CMakeFiles/ospTutorialC.dir/build.make:100: ospTutorialC] Error 1
make[1]: *** [CMakeFiles/Makefile2:178: builddir/ospray/intel64/CMakeFiles/ospTutorialC.dir/all] Error 2
make: *** [Makefile:150: all] Error 2

gucong commented on 2016-11-30 15:10

According to https://github.com/ospray/OSPRay/issues/110 , ospray doesn't build with community/embree which is configured with SSE2 only. I will revert to embree-isa.

chuckdaniels commented on 2016-11-30 11:14

@eolianoe @gucong Then, the dependency must be reverted to 'embree-isa'.

eolianoe commented on 2016-11-30 10:11

@gucong & @chuckdaniels: sorry for the noise I didn't check all the compilation, I also need embree-isa.

gucong commented on 2016-11-29 19:30

@chuckdaniels I doubt this will be fixed in community/embree, because it is supposed to work on the oldest machines (https://bugs.archlinux.org/task/51801). My ISA detection fix is only at build time, not at run time. However, something could possibly be done in cmake configurations in OSPRay to fix the linking problem, which I had no success just yet. A bug report upstream to OSPRay in this regard might be helpful.

Afterall, I see no benefit using the community build which forces older ISA and thus lower performances, just from a user's perspective.