[Paraview] request general advice for building paraview on x86-64 Opteron

[Berk Geveci]

Some of these problems seem to be fixed on cvs cmake (which is what I
installed on the 64 bit machines). I was told there is going to be a
cmake release in the near future to fix these problems.

-Berk

On 5/18/05, Lee A Ankeny <laa at lanl.gov> wrote:
> You shouldn't have to hack the makefiles, but I did find it necessary to add these to my cmake configuration:
> 
> CMAKE_EXE_LINKER_FLAGS:STRING=-L/usr/lib64 -L/usr/X11R6/lib64
> OPENGL_gl_LIBRARY:FILEPATH=/usr/lib64/libGL.so
> OPENGL_glu_LIBRARY:FILEPATH=/usr/lib64/libGLU.so
> X11_X11_LIB:FILEPATH=/usr/X11R6/lib64/libX11.so
> 
> That fixes most of my 64-bit Linux build problems. However, tk/.../wish doesn't get the message, and won't build properly unless you hack it's Makefile. Fortunately wish doesn't really matter, as it's not used for anything. See bug# 1823.
> 
> Lee
> 
> At 10:25 AM +0200 5/18/05, John Biddiscombe wrote:
> >>I recently build paraview on Intel EMT. I encountered one compile
> >>error (linker actually) while linking to MPICH I compiled myself. I
> >>was linking against a static mpich library and the linker complained I
> >>had to recompile mpich with fpic. When I linked against a shared
> >>mpich, everything worked fine. I should note that I was building
> >>paraview shared too. I did not try static.
> >>
> >>>Would anyone be willing to share their experience or advice for building ParaView and / or VTK on the x86-64 platform? I greatly appreciate any comments or suggestions you may have.
> >>>
> >>>
> >
> >I'll Second this. Anything you build yourself will be fine, because you can control the flags, but watch out for any third party libs you link against. I had a lot of trouble on a red hat box because it would link by default to everything in /usr/lib and I had to manually edit makefiles to link against /usr/lib64 in particular when running cmake, make sure you don't pick up the wrong libs in some of the X11R6/... directories and modify all the paths if necessary. I'm not sure how many distributions use lib and lib64 as distinct and different - but I found fedora core 3 was a lot of trouble in this respect. However if you know what you're doing (and I didn't because I'm new to linux), then you should be fine.
> >
> >JB
> >
> >
> >--
> >John Biddiscombe,                            email:biddisco @ cscs.ch
> >http://www.cscs.ch/about/BJohn.php
> >CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
> >Via Cantonale, 6928 Manno, Switzerland      | Fax:  +41 (91) 610.82.82
> >
> >
> >_______________________________________________
> >ParaView mailing list
> >ParaView at paraview.org
> >http://www.paraview.org/mailman/listinfo/paraview
> 
> --
> -------------------------------------------------------------------
> Lee Ankeny
> Group CCN-12, MS B295, Los Alamos, NM 87545
> 505-665-0195, FAX 505-665-5402, e-mail laa at lanl.gov
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview
>