[gadieid]

Hi.
My operating system is Ubuntu 18.04.2 out of the box and I am trying to compile OpenFoam 6.x from source using these instructions:

https://openfoamwiki.net/index.php/I...u#Ubuntu_18.04

The computer includes a simple NVIDIA card (GT710)

The source code is downloaded with git
git clone https://github.com/OpenFOAM/OpenFOAM-6.git
git clone https://github.com/OpenFOAM/ThirdParty-6.git

The reason I am compiling is that I want to compile Paraview with python (I am using anaconda 2.7 latest distribution)

MPi version is Open MPI 2.1.1

So my compilation line looks like this:

./makeParaView -python -mpi -python-lib /home/eyal/anaconda2/lib/libpython2.7.so.1.0 > log.makePV 2>&1

And repeatedly get this error:

[ 87%] Linking CXX static library ../../lib/libvtkPVServerManagerRenderingCS-pv5.4.a
[ 87%] Built target vtkPVServerManagerRenderingCS
Makefile:151: recipe for target 'all' failed
make: *** [all] Error 2
Command exited with non-zero status 2

The OF itself pass compilation without any problems.
As a workaround I use the PV from previous Of version (PV 4.4) but would like to be able to compile the new one.
Any help will be apprecaite,
Thanks
Gadi

[wyldckat]

Quick answer: The error lines you provided tell us nothing useful The complete "log.makePV" you tell us a lot more.

That said, you're using another Python installation, so the build scripts might be getting confused, due to multiple Python 2.7 versions...

Run:

./makeParaView -help

and check what other options exist for Python settings...

An example from here: https://openfoamwiki.net/index.php/I...HEL#CentOS_6.8

./makeParaView -qt-4.8.6 -mpi -python -python-lib /opt/rh/python27/root/usr/lib64/libpython2.7.so -python-include /opt/rh/python27/root/usr/include/python2.7 > log.makePV 2>&1

which you can see, it uses the option "-python-include"...

[gadieid]

Thanks for your input. I will try to attach the full log.
As you mentioned, I am using a different Python package. It worked in previous version of OF/PV (3 and 4) and the only change needed was to supply the new pythonlib.
My mistake was that i presumed it will work on these version as well.

In PV5.4 the python-include-dir is new and I tried to set it as well, but there was no difference in the results.

I tried to remove the -python at all (and change the makeParaView file to have python=false) but the same problem occurred (I suspect that it still tries to compile with python).

The last attempt was to use a clean environment with the OS-out-of-the-box python, and use the exact lines of the instructions. That worked!

So indeed the blame is on me, trying different Python. I might try a lower Anaconda version and see if it will work, or simply install all the libraries I need in the OD python. but at least there is some focus on the source of the problem.

However if you have the time and can glance in the full log of the bad compilation this will be great.

Thanks for your help!
Gadi.

[wyldckat]

Quick answer: So what broke the build was this:

/usr/lib/x86_64-linux-gnu/libSM.so: undefined reference to `uuid_generate@UUID_1.0'
/usr/lib/x86_64-linux-gnu/libSM.so: undefined reference to `uuid_unparse_lower@UUID_1.0'
collect2: error: ld returned 1 exit status
Utilities/LegacyColorMapXMLToJSON/CMakeFiles/vtkLegacyColorMapXMLToJSON.dir/build.make:199: recipe for target 'bin/vtkLegacyColorMapXMLToJSON' failed
make[2]: *** [bin/vtkLegacyColorMapXMLToJSON] Error 1
CMakeFiles/Makefile2:14852: recipe for target 'Utilities/LegacyColorMapXMLToJSON/CMakeFiles/vtkLegacyColorMapXMLToJSON.dir/all' failed
make[1]: *** [Utilities/LegacyColorMapXMLToJSON/CMakeFiles/vtkLegacyColorMapXMLToJSON.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....

Searching online for the first error line gave me this: https://discourse.paraview.org/t/pv-...nd-uuid/884/14

So my guess is that there is a library in the Anaconda library stack that contaminated the build environment and affected the build.

I know I did use with success the Anaconda software stack back in 2016 to build ParaView et al, but apparently something went wrong with the build you have of Anaconda and Ubuntu 18.04.

Technically, as long as the two Python versions are identical or nearly identically (e.g. Python 2.7.13 and 2.7.14), you can now activate the shell environment for Anaconda on top of OpenFOAM and ParaView should pick up Anaconda's Python version and complete Python stack. This way you can get the best of both worlds: no headache building ParaView and have the complete Anaconda stack


----
Edit: I remember now where I wrote about using Anaconda... it's written here:

• https://openfoamwiki.net/index.php/I...oam-extend_4.0
• https://openfoamwiki.net/index.php/I...OpenFOAM_3.0.x

And yes, it was used by both OpenFOAM and foam-extend.

[gadieid]

Thanks for the help!

[CallumG]

Has this ever been resolved? I have the same issue with the Third Party ./Allmake for OpenFOAM-6 on Ubuntu 18.04 (log attached). I think it's exactly the same issue, but from reading this thread and the one linked on the PV website I'm not sure I can fathom how to resolve it?

I followed the wiki instructions to a t:
https://openfoamwiki.net/index.php/I...u#Ubuntu_18.04

Apologise I'm inexperieced with compiling/building code so I may have missed what I actually need to do to get it to build? Is there any chance anyone could give me a bit of a steer on how I go about getting this to work?

[leonpjv]

Hi Callum,

I realise this is too late to help you but may help someone else.

As wyldckat pointed out, Anaconda may cause issues with the build.

What I did to avoid anaconda interfering was:
1. Comment out the lines in the ~/.bashrc file which export the anaconda path. Look for the lines ">>> conda initialize >>>" and "<<< conda initialize <<<", and then comment out between them.
2. open a new terminal for changes to take effect.
3. then run ./makeParaView

This worked for me. You can uncomment afterwards (undo step 1).

[joshwilliams]

Originally Posted by leonpjv

Hi Callum,

I realise this is too late to help you but may help someone else.

As wyldckat pointed out, Anaconda may cause issues with the build.

What I did to avoid anaconda interfering was:
1. Comment out the lines in the ~/.bashrc file which export the anaconda path. Look for the lines ">>> conda initialize >>>" and "<<< conda initialize <<<", and then comment out between them.
2. open a new terminal for changes to take effect.
3. then run ./makeParaView

This worked for me. You can uncomment afterwards (undo step 1).

This is good advice. But a cleaner option than commenting/uncommenting code is to simply do "conda deactivate" before compiling. Then you may do "conda activate" after to restore your base python env.

[shixuemozun]

When i run ./makeParaView

there are some troubles:

Makefile:152 all Error 2
Command exited with non-zero status 2