[praphul]

Hi,

I encounter trouble in building ParaviewV5.6.0 with python and mpi support which comes along the ThirdPartyV1812 suite of OpenFoam. The following is the output log of the build process at 89% after which the build crashes.

[ 89%] Building CXX object VTK/Wrapping/Python/CMakeFiles/vtkPVClientServerCoreRenderingPythonD.dir/vtkPVClientServerCoreRenderingPythonInitImpl.cxx.o
[ 89%] Linking CXX shared library ../../../lib/libvtkPVClientServerCoreRenderingPython27D-pv5.6.so
[ 89%] Built target vtkPVClientServerCoreRenderingPythonD

.



Build worked fine when no mpi and python support was provided. The main reason as to why I require a python support is to use the Python shell. Therefore, I used the following command to compile Paraview with mpi and python support.

./makeParaView -qt-5.12.0 -mpi -python-lib /usr/lib/python2.7 -python-bin /usr/bin/python2.7

Any idea so as to why the build fails ?

[wyldckat]

Greetings praphul,

Originally Posted by praphul

Any idea so as to why the build fails ?

Yes, I do have multiple ideas as to why, but I don't have enough evidence to know the exact solution.

The first idea that came to mind was that given the lack of details, the reason why it failed was because not enough was known to ensure that it would work.
Sorry, it's a dumb answer, but given the lack of information, my brain didn't cooperate...

So, what's missing:

1. Which Linux Distribution, version and architecture are you using?
2. Which installation instructions are you following?
3. Which system packages did you install?
4. The output you provided... is not an error message... so it's nearly useless... the missing crash/error details would tell us what went wrong... The best we get out of it is that it might have stopped compiling due to something missing from Python... so this is where I usually ask for a complete log file. So please run the command you used, but like this:
   

   ./makeParaView -qt-5.12.0 -mpi -python-lib /usr/lib/python2.7 -python-bin /usr/bin/python2.7 > log.makePV 2>&1

   • Then package the resulting log file and attach it to your next post... you can package it by running this command:
     

     gzip < log.makePV > log.makePV.gz

     Then attach the file "log.makePV.gz" to your next post.

My second idea/suspicion is this:

-python-lib /usr/lib/python2.7

This seems like an incomplete definition and it's not a proper one at that. Usually it's either something like this:

-python-lib $PYTHONHOME/lib/libpython2.7.so

or something like this:

-python-lib /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0

Other ideas:

1. Ran out of disk space.
2. CPU bug which lead to a crash by the compiler.
3. CPU overheating...
4. RAM problems...
5. MPI incorrectly configured...
6. Ambiguity of Python versions... although this one doesn't make much sense, since you've pointed out the folder names for a specific version... but it could happen, if it picked up the wrong "include" folder.
7. Python 2.7 not being fully installed... I have seen this happen in the past, when a custom build was attempted by someone not experienced enough...
8. Uh... accidentally pressing Ctrl+C?
9. Someone else was controlling your computer...
10. MS Windows intervened... somehow... I don't know, but if you were working in WSL, I would suspect that Windows updating automatically could result in such a situation... where it rebooted while you were away and all that was left was the incomplete log file...
11. Hard-drive failure in a specific sector when it was trying to write the built library to disk...
12. You made a bet with someone and that was why you wrote the post the way you did... I tend to be paranoid about that, when I read posts like this...
13. Power supply problems...
14. Graphics card problems... if somehow the driver crashed and restarted itself... but just the driver...

I could conjure up more ideas, but... I feel bad for already poking at you for your honest question "any idea?"... but the lack of information just tilted me the wrong way...

Best regards,
Bruno

[praphul]

Hi Bruno,

Thanks for the reply.

I apologize for not giving extra details on this issue. I had dumped out the log file earlier but I didn't redirect stderr which resulted in a file without the error message. Therefore, the end of output log file only had the information which I had posted as a code snippet.

The second suspicion of yours proved to be right. I had defined the python libraries incorrectly. Paraview has now been build and installed properly when I changed the makeParaView command to the following.

./makeParaView -qt-5.12.0 -mpi -python-include /usr/include/python2.7 -python-lib /usr/lib/x86_64-linux-gnu/libpython2.7.so

I had to keep aside all other ideas you had mentioned while debugging the solution because I tried building the third party ParaView in a fresh install of Manjaro 18.04 (in another system) and found the python library to be defined in a similar manner as you had suggested in the log file.



Thanks a lot for the the suggestion.

I have a couple more questions.

1. After the installation is complete, is it necessary to setup LD_LIBRARY_PATH manually ? ParaviewV5.6.0 seems to be working without any problems as of now.
2. Can I remove the Paraview version 5.4.1 installed from the apt repository ? Will the removal cause any further troubles on the newly installed ParaviewV5.6.0 in ThirdParty? My system is KubuntuV18.10.

TYI : I have just started my OpenFoam journey.



Regards,
Praphul

[wyldckat]

Quick answers:

Originally Posted by praphul

1. After the installation is complete, is it necessary to setup LD_LIBRARY_PATH manually ? ParaviewV5.6.0 seems to be working without any problems as of now.

Everything should be automatically done by OpenFOAM's bashrc scripts. When you open a new terminal and activate the OpenFOAM shell environment (namely to use the source command), everything should work as intended.

Originally Posted by praphul

2. Can I remove the Paraview version 5.4.1 installed from the apt repository ? Will the removal cause any further troubles on the newly installed ParaviewV5.6.0 in ThirdParty? My system is KubuntuV18.10.

It's preferable to remove ParaView 5.4.1 that you installed via apt, just to avoid accidental library collisions between the two versions. There shouldn't be any problems, but just in case, might as well avoid conflicts between them if you don't need 5.4.1.

Removing it should not affect ParaView 5.6.0, or at least it should not.
It is possible that some package might be uninstalled when ParaView 5.4.1 is uninstalled (apt will tell you about the ones that were picked to be uninstalled), but you can then re-install those package(s) via apt.

[praphul]

Thanks Bruno for the help. Everything is perfect now.