[mdhfiz]

I am trying to get my hands on OF7 but when I was trying to compile ParaView, I get this error:

Version information
    qt        5.9.3
    version   5.6.0
    major     5.6
    build     Release
MISMATCH!
    specified 5.6.0
    found

and also:

CMake Error at /usr/lib64/cmake/Qt5/Qt5Config.cmake:28 (find_package):
  Could not find a package configuration file provided by "Qt5X11Extras" with
  any of the following names:

    Qt5X11ExtrasConfig.cmake
    qt5x11extras-config.cmake

I was using this command and arguments to make paraview:

./makeParaview -qmake /usr/local/Qt-5.9.3/bin/qmake -python -mpi > log.makePV 2>&1

I am using OpenSUSE 15.1 btw.

I have attached my log file alongside this thread. What's the solution for this?

[wyldckat]

Quick answer: I've started writing instructions for this at openfoamwiki.net here: https://openfoamwiki.net/index.php/I...SUSE_Leap_15.1 - I'm still testing it, but have gotten ParaView to start compiling without problems.

In step #2 are the commands for installing the necessary packages. No need to install Qt 5.9.3 as a side installation, given that Qt 5.9.7 is provided with openSUSE 15.1.

edit: In step #9 are the commands needed for building ParaView...

[gcengineer]

I just posted a procedure for building ParaView 5.6.0 with Qt5 for OpenFOAM-7 and for OpenFOAM-v1906 running under Ubuntu 18.04.


Qt5, OpenFOAM-7 and -v1906, and Ubuntu 18.04

[wyldckat]

@gcengineer: openSUSE is a bit of different beast from Ubuntu... for example, I needed the fix for xmlpatterns that is provided here: https://build.opensuse.org/package/v...patch?expand=0 - this is because in openSUSE there is nothing similar to the "qt5-default" package on Ubuntu...


@mdhfiz: I've finished testing to build ParaView 5.6.0 and updated the wiki page accordingly: https://openfoamwiki.net/index.php/I...SUSE_Leap_15.1
As mentioned in the previous paragraph, I had to apply a fix to the code in order for things to fully work as intended.

In the meantime, I'm leaving the machine running overnight, to see if it builds OpenFOAM 7 properly...

edit: Built successfully.

[mdhfiz]

@wyldckat it works fine, thanks bruno!

[mateusdias89]

Hello,


I'm using OpenSUSE Leap 15.0. I followed all the exact instructions proposed by @wyldckat but I'm still getting the following compilation error:

[ 94%] Building CXX object VTK/Wrapping/Python/CMakeFiles/vtkPVServerManagerDefaultPythonD.dir/vtkSMViewExportHelperPython.cxx.o
[  94%] Building CXX object  VTK/Wrapping/Python/CMakeFiles/vtkPVServerManagerDefaultPythonD.dir/vtkSMXYChartRepresentationInitializationHelperPython.cxx.o
[  94%] Building CXX object  VTK/Wrapping/Python/CMakeFiles/vtkPVServerManagerDefaultPythonD.dir/vtkPVServerManagerDefaultPythonInitImpl.cxx.o
[ 94%] Linking CXX shared library ../../../lib/libvtkPVServerManagerDefaultPython27D-pv5.6.so
[ 94%] Built target vtkPVServerManagerDefaultPythonD
make: *** [Makefile:152: all] Error 2

real    18m35.794s
user    124m56.524s
sys    22m38.440s

Alternatively, I tried compiling without python flag but still got an error message. I'm attaching the log files here: https://drive.google.com/file/d/1QZy...ew?usp=sharing



Does anyone know how to solve this problem?


Best,

Mateus

[wyldckat]

Quick answer: The actual error message in the build with Python is this:

[ 94%] Linking CXX shared library ../../lib/libvtkpqCore-pv5.6.so
/usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: ../../lib/libvtkpqWidgets-pv5.6.so.1: _edata: invalid version 21 (max 0)
/usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: ../../lib/libvtkpqWidgets-pv5.6.so.1: error adding symbols: bad value

While the error without Python is this:

[ 90%] Linking CXX shared library ../../lib/libvtkpqCore-pv5.6.so
/usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: ../../lib/libvtkpqWidgets-pv5.6.so.1: _edata: invalid version 21 (max 0)
/usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: ../../lib/libvtkpqWidgets-pv5.6.so.1: error adding symbols: bad value

which is pretty much the same...

This is really strange... OK, a bit of searching online and it might be a bug in binutils: https://gitlab.kitware.com/paraview/...uild/issues/99

What does the following command give you?

ld --version

If it tells you that the version is 2.30. ... then that might the problem, in which case you need yo update your binutils package in your OpenSUSE installation.

[mateusdias89]

Originally Posted by wyldckat

Quick answer: The actual error message in the build with Python is this:

[ 94%] Linking CXX shared library ../../lib/libvtkpqCore-pv5.6.so
/usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: ../../lib/libvtkpqWidgets-pv5.6.so.1: _edata: invalid version 21 (max 0)
/usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: ../../lib/libvtkpqWidgets-pv5.6.so.1: error adding symbols: bad value

While the error without Python is this:

[ 90%] Linking CXX shared library ../../lib/libvtkpqCore-pv5.6.so
/usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: ../../lib/libvtkpqWidgets-pv5.6.so.1: _edata: invalid version 21 (max 0)
/usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: ../../lib/libvtkpqWidgets-pv5.6.so.1: error adding symbols: bad value

which is pretty much the same...

This is really strange... OK, a bit of searching online and it might be a bug in binutils: https://gitlab.kitware.com/paraview/...uild/issues/99

What does the following command give you?

ld --version

If it tells you that the version is 2.30. ... then that might the problem, in which case you need yo update your binutils package in your OpenSUSE installation.

Thank you for your answer!

This is what I got:

GNU ld (GNU Binutils; openSUSE Leap 15.0) 2.31.1.20180828-lp150.5.3
Copyright (C) 2018 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) a later version.
This program has absolutely no warranty.

I will upgrade it and try again. I will let you if I'm successful.

Mateus

[wyldckat]

Quick question: How many cores does your machine have and how much RAM?

I ask this because it could be due to not enough RAM... I had done a test run with 4 cores and 4GB of RAM inside a virtual machine, but had problems because it would crash due to not enough RAM... but I don't remember what was the error message it gave me...

[mateusdias89]

Originally Posted by wyldckat

Quick question: How many cores does your machine have and how much RAM?

I ask this because it could be due to not enough RAM... I had done a test run with 4 cores and 4GB of RAM inside a virtual machine, but had problems because it would crash due to not enough RAM... but I don't remember what was the error message it gave me...

The machine has 6 cores (12 threads) and 32 GBs of ram. During the compilations I always had at least 20 GBs of ram available. So this is definitely not the issue.

However, I just checked and the current version I have already is the latest version. In the link you sent to me, they said they were able to compile downgrading binutils, instead of upgrading. I will try it and see what happens.

Thanks,
Mateus

[wyldckat]

Quick note: The ld version I used on my VM was this:

 2.31.1.20180828-lp151.2

The binutils package version that is indicated by OpenSUSE's YaST2 is:

2.31-lp151.2.29-x86_64

It's possible you are using a version from another repository that is not the one meant for OpenSUSE 15.1?

Oh... wait, you're using OpenSUSE 15.0... I don't remember if OpenSUSE has a clear upgrade path from 15.0 to 15.1...

[mateusdias89]

Originally Posted by wyldckat

Quick note: The ld version I used on my VM was this:

 2.31.1.20180828-lp151.2

The binutils package version that is indicated by OpenSUSE's YaST2 is:

2.31-lp151.2.29-x86_64

It's possible you are using a version from another repository that is not the one meant for OpenSUSE 15.1?

Oh... wait, you're using OpenSUSE 15.0... I don't remember if OpenSUSE has a clear upgrade path from 15.0 to 15.1...

Thank you for the info! This is the version I had before. I ended up having to downgrade binutils to version 2.29.1. After that, I was able to compile it until getting another error, but this time at 100%:

[100%] Building CXX object Plugins/StreamLinesRepresentation/CMakeFiles/StreamLinesRepresentation.dir/moc_StreamLinesRepresentation_Plugin.cpp.o
[100%] Linking CXX shared library ../../lib/paraview-5.6/plugins/NonOrthogonalSource/libNonOrthogonalSource.so
[100%] Built target NonOrthogonalSource
/usr/lib64/libSM.so: undefined reference to `uuid_generate@UUID_1.0'
/usr/lib64/libSM.so: undefined reference to `uuid_unparse_lower@UUID_1.0'
collect2: error: ld returned 1 exit status
make[2]: *** [Applications/ParaView/CMakeFiles/paraview.dir/build.make:328: bin/paraview] Error 1
make[1]: *** [CMakeFiles/Makefile2:58555: Applications/ParaView/CMakeFiles/paraview.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[100%] Linking CXX shared library ../../lib/paraview-5.6/plugins/StreamLinesRepresentation/libStreamLinesRepresentation.so
[100%] Built target StreamLinesRepresentation
make: *** [Makefile:152: all] Error 2

I googled for a solution and found this: https://discourse.paraview.org/t/pv-...nd-uuid/884/19

So the solution that worked for me was to add the following code before the first include statement in the CMakeList.txt file:

SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -luuid")

And this did the job for me! I'm putting all the details here, so that hopefully someone with the same issue can find this page after a quick google search.

Bruno, thank you for that step by step procedure! If it was hard with that, imagine if I didn't have had to begin with. And also for pointing out the issue with binutils!

Best,

Mateus

[CLF]

Following the excellent Instructions on openfoamwiki about the Installation procedure for OF7 on Leap 15.1, upgraded from Tumbleweed, the Installation went flawlessly, when two additional issues were fixed:



1. Paraview complained about a missing "asm/errno.h" file. This was due to the directory "/usr/include/asm" being initially empty and was fixed by a symlink to /usr/include/arch-x86/asm", which may differ for other cases.



2. OF7 complained about some missing "metis" declarations, using the system metis. Adding the directory "bin" to the third line in Nr. 6 of the Instructions
echo "export METIS_ARCH_PATH=/usr/bin"...

fixed this.

Just my 2c.

[wyldckat]

Hi CLF,

Many thanks for the information!
But I'm a bit confused...

1. Did you upgrade from 15.1 to Tumbleweed and/or did you follow the installation instructions directly in Tumbleweed?
2. Or did you upgrade from Tumbleweed into 15.1?

In addition, did you install the 32-bit or the 64-bit architecture of openSUSE? Or did you install both architectures?

Best regards,
Bruno

[CLF]

@wyldckat


Thanks for Your response.

First of all, I want to thank You very much for the tremendous effort You undertook supporting OF.

To Your Questions:


I did 2.: "upgrade" from Tumbleweed-x86_64-Snapshot 20191207 to Leap 15.1-x86.64
Therefore, I am running a 64 bit System.

However, compilation was done for 32 bit Integer support, following point 7 in openfoamwiki.net/Installation/Linux/OpenFOAM-7/openSUSE/Leap_15.1.

Hoping, that this answers Your Questions.

Sincerely,

CLF

[wyldckat]

Hi CLF,

You're welcome and many thanks!

So my doubt here is that Tumbleweed is meant to be the bleeding edge development line of openSUSE and Leap is the stable development line. So from one perspective, it's a downgrade going from Tumbleweed to Leap, given that you must have went back on the versions for several of the packages made available in openSUSE.

This to say that without testing this myself, I'm not sure if the bugs you've found and reported were due to Tumbleweed and not Leap 15.1.

That said, I have seen openSUSE do some strange changes within the same version, so it's possible that Metis changed it's installation procedure within Leap 15.1 after I wrote those instructions on the wiki. I'll have to go through them once again, to check if anything/what changed.

Best regards,
Bruno