Anyone built on Fedora 35 yet?

[freman]

Hi,

I just has the misfortune of "upgrading" to Fed35 since Fed34 is near EOL. Big mistake.

It seems loads of packages have not survived the update and are no longer installed. I've yet to work out if this is some renaming of lack or inclusion in F35.

boost* and lots of *devel files don't seem to be recognised any more.
[EDIT] It seems the problem is something is trying to load old python and boost library versions. See below.

Anyone tried building master on Fed 35 yet , who can advise on tips or whether this is even possible ?
TIA.

This maybe part of the problem. The update moves from python 3.9 to 3.10.4 , shiboken seems to be missing this in cmake:

Code: Select all

-- Checking for module 'Coin'
--   Found Coin, version 4.0.0
-- Coin3D libraries found
-- Shiboken2Config: Using default python: .cpython-310-x86_64-linux-gnu
-- Found PythonInterp: /usr/bin/python3 (found suitable version "3.10.4", minimum required is "3") 
-- Found PythonLibs: /usr/lib64/libpython3.9.so (Required is at least version "3") 
-- SHIBOKEN_PYTHON_INCLUDE_DIRS computed to value: '/usr/include/python3.9'
-- SHIBOKEN_PYTHON_LIBRARIES computed to value: ''
-- libshiboken built for Release
-- PYTHON_CONFIG_SUFFIX: .cpython-310-x86_64-linux-gnu
-- libshiboken built for Release

Code: Select all

dnf install python3-shiboken2-devel  python3-pyside2-devel

Last metadata expiration check: 1:51:20 ago on Mon 09 May 2022 10:17:56 CEST.
Package python3-shiboken2-devel-1:5.15.2-5.fc35.x86_64 is already installed.
Package python3-pyside2-devel-1:5.15.2-5.fc35.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!

[freman]

I seem to have cleared the shiboken problem. Make clean does not work but a manual rm -rf in the build dir does.

Hmm, it built OK, but still something pulling in the old python ...

Code: Select all

 ldd /svn/freecad-build/bin/FreeCAD
        linux-vdso.so.1 (0x00007ffff2545000)
        libmpi_cxx.so.40 => /usr/lib64/openmpi/lib/libmpi_cxx.so.40 (0x00007f441c42f000)
        libmpi.so.40 => /usr/lib64/openmpi/lib/libmpi.so.40 (0x00007f441c301000)
        libFreeCADGui.so => /svn/freecad-build/lib/libFreeCADGui.so (0x00007f441a15f000)
        libFreeCADApp.so => /svn/freecad-build/lib/libFreeCADApp.so (0x00007f441910e000)
        libFreeCADBase.so => /svn/freecad-build/lib/libFreeCADBase.so (0x00007f4418dec000)
        libxerces-c-3.2.so => /lib64/libxerces-c-3.2.so (0x00007f4418a4a000)
        libz.so.1 => /lib64/libz.so.1 (0x00007f4418a30000)
        libpython3.9.so.1.0 => not found
        libutil.so.1 => /lib64/libutil.so.1 (0x00007f4418a2b000)

plus a bunch of boost related stuff:

Code: Select all

        /lib64/ld-linux-x86-64.so.2 (0x00007f441c44b000)
        libboost_filesystem.so.1.75.0 => not found
        libboost_program_options.so.1.75.0 => not found
        libboost_regex.so.1.75.0 => not found
        libboost_system.so.1.75.0 => not found
        libboost_thread.so.1.75.0 => not found
        libboost_date_time.so.1.75.0 => not found
        libboost_chrono.so.1.75.0 => not found
        libboost_atomic.so.1.75.0 => not found
        libpyside2.cpython-39-x86_64-linux-gnu.so.5.15 => not found
        libpython3.9.so.1.0 => not found
        libshiboken2.cpython-39-x86_64-linux-gnu.so.5.15 => not found
        libboost_filesystem.so.1.75.0 => not found
        libboost_program_options.so.1.75.0 => not found
        libboost_regex.so.1.75.0 => not found
        libboost_system.so.1.75.0 => not found
        libboost_thread.so.1.75.0 => not found
        libboost_date_time.so.1.75.0 => not found
        libboost_chrono.so.1.75.0 => not found
        libboost_atomic.so.1.75.0 => not found
        libpython3.9.so.1.0 => not found
        libboost_filesystem.so.1.75.0 => not found
        libboost_program_options.so.1.75.0 => not found
        libboost_regex.so.1.75.0 => not found
        libboost_system.so.1.75.0 => not found
        libboost_thread.so.1.75.0 => not found
        libboost_date_time.so.1.75.0 => not found
        libboost_chrono.so.1.75.0 => not found
        libboost_atomic.so.1.75.0 => not found
        libpython3.9.so.1.0 => not found
        libexpat.so.1 => /lib64/libexpat.so.1 (0x00007f441633f000)

PS I have rebuilt OCL and OCCT locally , Coin4 and pivy are distro. I can't see what else is still linked to old boost.

[freman]

any tips on how I can find what is attempting to load these out of date libraries ?

[paullee]

@PrzemoF has a COPR which build Fedora rpm?

I had long used AppImage version on Fedora though

[freman]

Thanks, I'm trying to build master.

[Haavard]

I have compiled on 35. I installed the following packages (i think):

Code: Select all

dnf install gcc-c++ cmake doxygen swig gettext dos2unix desktop-file-utils libXmu-devel freeimage-devel mesa-libGLU-devel opencascade-devel openmpi-devel python3 python3-devel python3-pyside2 python3-pyside2-devel pyside2-tools boost-devel tbb-devel eigen3-devel qt-devel qt-webkit-devel qt5-qtxmlpatterns qt5-qtxmlpatterns-devel qt5-qtsvg-devel qt5-qttools-static ode-devel xerces-c xerces-c-devel opencv-devel smesh-devel Coin3 Coin3-devel SoQt-devel freetype freetype-devel vtk vtk-devel med med-devel libspnav-devel python3-pivy python3-markdown python3-GitPython

It works here, but i have to run the binary in a xorg session, the performance is terrible in wayland (even though appimages works great).

[freman]

Thanks, I don't think it's a case of a missing package, it compiles fully . Except that something is getting loaded which is pulling in old versions of some libs. Maybe I'm forgetting another file which I compiled from source.

Hmm, this may be pertinent:

Code: Select all

ls /usr/lib/python3.9/site-packages
camvtk.py  chardet  initial_setup  packaging  procmemory.py  pyglet  pygments  pyocl.py  requests  STLTools.py

I'm not sure why any of that is there now. There are four items which are files ( not directories ): camvtk.py pyocl.py STLTools.py procmemory.py, with the same datestamp 27th April. ( about two weeks old just before I did the Fed35 move ). They all look to be FreeCAD related. The same items appear in /usr/lib/python3.10/site-packages dated for today : current build.

I moved them to /tmp but not fixed.
Ah, I just found this in ./bashrc :

Code: Select all

PIP_PACKAGES="~/.local/lib/python3.9/site-packages"

That gets added to $PATH

[adrianinsaval]

as always pip wrecking havoc it's weird for that to be in your bashrc though, perhaps you manually added it in the past?

[freman]

Yes, I think I did that by hand , o/w it would not be in the PATH.

I suppose that means I have to pip uninstall everything every time there is a major python upgrade or a distro upgrade.