Bug 834991 – media-gfx/freecad-0.19.2-r6 Could NOT find Boost: Found unsuitable version "1.78.0", but required is exact version "1.77.0"

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Alessandro Barbieri 2022-03-12 09:58:29 UTC]

This package fails to build on an unstable system. Attached relevant logs and emerge --info

[Comment 1 Alessandro Barbieri 2022-03-12 09:58:34 UTC]

Created attachment 766849 [details]
emerge_info

emerge --info

[Comment 2 Alessandro Barbieri 2022-03-12 09:58:35 UTC]

Created attachment 766850 [details]
freecad-0.19.2-r6:20220312-095656.log

build log

[Comment 3 Matthew Smith 2022-03-12 10:21:03 UTC]

I'm not able to reproduce this, I have freecad-0.19.2-r6 and boost-1.78.0-r2.

Excerpts from log (attached):

    $ grep -i boost /var/tmp/portage/media-gfx/freecad-0.19.2-r6/temp/build.log
     * Applying freecad-0.19.2-0006-add-boost-serialization-to-find_package.patch ...
    -- Found Boost: /usr/lib64/cmake/Boost-1.78.0/BoostConfig.cmake (found suitable exact version "1.78.0")
    -- Found Boost: /usr/lib64/cmake/Boost-1.78.0/BoostConfig.cmake (found suitable exact version "1.78.0") found components: serialization
    -- Found Boost: /usr/lib64/cmake/Boost-1.78.0/BoostConfig.cmake (found suitable version "1.78.0", minimum required is "1.55") found components: filesystem program_options regex serialization system thread
    -- Boost:               1.78.0 (1.78.0)

Since 'Found Boost' and 'Could NOT find Boost' appear multiple times in your build log, could it be that an old version of one of the deps (not FreeCAD itself) requires boost 1.77?

[Comment 4 Bernd 2022-03-12 12:38:38 UTC]

Thanks for your report, Allessandro.

There seems to be an issue with either pcl, vtk or liblas, as far as I can see from the output. LibLAS is only included with vtk when the all-modules USE flag is used.
To narrow this down, could you please try, if rebuilding vtk without this USE flag changes anything? Or try rebuilding liblas? Of course, both with boost-1.78.0 active.

[Comment 5 Alessandro Barbieri 2022-03-12 16:14:33 UTC]

Rebuilding vtk solved this

[Comment 6 Bernd 2022-03-12 17:37:32 UTC]

Thanks for testing on this.

Did you rebuild with USE="all-modules" or without this use flag?

[Comment 7 Alessandro Barbieri 2022-03-12 20:36:44 UTC]

I have rebuilt it with USE="all-modules"

[Comment 8 Bernd 2022-03-12 22:42:55 UTC]

I feared this might be the cause of this, but that seems not be the case.
Thanks again!