[Paraview] SOLVED Re: Paraview 4.4.0 build error with osmesa on RHEL cluster at LLNL

[Cook, Rich]

I ended up fixing the problem by appending " -lGLU" to my LINKER_FLAGS, which I add to all my CMAKE_XXXX_FLAGS as follows: 

-DCMAKE_EXE_LINKER_FLAGS:STRING="$LINKER_FLAGS" \
        -DCMAKE_SHARED_LINKER_FLAGS:STRING="$LINKER_FLAGS" \
        -DCMAKE_EXE_LINKER_FLAGS_DEBUG:STRING="$LINKER_FLAGS" 

The build now completes successfully. 


> On Oct 30, 2015, at 11:54 AM, Ben Boeckel <ben.boeckel at kitware.com> wrote:
> 
> On Fri, Oct 30, 2015 at 18:22:01 +0000, Cook, Rich wrote:
>> I'm seeing an error when trying to build the latest Paraview using
>> osmesa:
>> 
>> The configuration step goes OK.  In particular note that I set
>> -DOPENGL_glu_LIBRARY:FILEPATH=/usr/lib64/libGLU.so
> 
> I think with OSMesa, this should be empty. Here is what our superbuild
> sets when using osmesa:
> 
>  -DOPENGL_INCLUDE_DIR:PATH=
>  -DOPENGL_xmesa_INCLUDE_DIR:PATH=
>  -DOPENGL_gl_LIBRARY:FILEPATH=
>  -DOPENGL_glu_LIBRARY:FILEPATH=
>  -DOSMESA_INCLUDE_DIR:PATH=<INSTALL_DIR>/include
>  -DOSMESA_LIBRARY:FILEPATH=<INSTALL_DIR>/lib/libOSMesa.so
> 
> Where <INSTALL_DIR> is /usr on a system-installed mesa. You can also use
> libOSMesa.a for a static mesa.
> 
> --Ben

-- 
✐Richard Cook   
✇ Lawrence Livermore National Laboratory
Bldg-453 Rm-4024, Mail Stop L-557        
7000 East Avenue,  Livermore, CA, 94550, USA
☎ (office) (925) 423-9605    
☎ (fax) (925) 423-6961
---
Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept.
(opinions expressed herein are mine and not those of LLNL)