Hello!
Thanks for that hint. I compared the Fedora specs [1] with the KitWare
recommendations [2]. The main difference (leaving --enable-{glx,dri,egl}
and related switches aside) seems to be that Fedora builds with
--enable-osmesa, while KitWare recommends --enable-gallium-osmesa. Both set
--with-gallium-drivers=swrast and --enable-gallium-llvm, though.
--Dennis
[1]: https://apps.fedoraproject.org/packages/mesa/sources/spec/
[2]: http://www.kitware.com/blog/home/post/999
On Wednesday, 3 February 2016 19:43:05 CET, Utkarsh Ayachit wrote:
I suspect OSMesa is not built with gallium/llvm driver and hence it's
failing to give a 3.2 context. I am a little rusty on where to find
info about Fedora packages. Can you check how the osmesa library is
being configured?
On Wed, Feb 3, 2016 at 12:19 PM, Dennis Schridde
<[email protected]> wrote:
Hello!
I built [1] ParaView 5.0.0 against OSMesa 11.2 from Git
(11.2.0-0.devel.8.24ea81a.fc24 from Fedora Rawhide [2]), but I am running
into following problem:
ERROR: In ...
--
Universität Heidelberg, Universitätsrechenzentrum (URZ)
Servicebereich Future IT - Research & Education (FIRE)
Tel. +49 6221 54-4519, Fax +49 6221 54-5581
[email protected]
http://www.urz.uni-heidelberg.de/
Ruprecht-Karls-Universität Heidelberg
Universitätsrechenzentrum
Im Neuenheimer Feld 293, 69120 Heidelberg
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView
Search the list archives at: http://markmail.org/search/?q=ParaView
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview
