[Slackbuilds-users] VTK

[Tim Dickson]

On 15/04/2023 02:46, Christoph Willing wrote:
> On 15/4/23 04:26, Tim Dickson via SlackBuilds-users wrote:
>> hi all, I'm getting the following error building VTK
>>
>> [ 99%] Linking CXX shared module 
>> ../../../lib64/qml/VTK.9.2/libqmlvtkplugin.so
>> Generating qmltypes file using qmlplugindump
>> QQmlComponent: Component is not ready
>> make[2]: *** 
>> [GUISupport/QtQuick/qml/CMakeFiles/qmlvtkplugin.dir/build.make:151: 
>> lib64/qml/VTK.9.2/libqmlvtkplugin.so] Error 3
>> make[2]: *** Deleting file 'lib64/qml/VTK.9.2/libqmlvtkplugin.so'
>> make[1]: *** [CMakeFiles/Makefile2:18427: 
>> GUISupport/QtQuick/qml/CMakeFiles/qmlvtkplugin.dir/all] Error 2
>> make: *** [Makefile:136: all] Error 2
>>
>> I have IMAGING=yes and MPI=yes flags set. (and openmpi installed)
>>
>> Any ideas?
>> regards, Tim
>
> Interestingly, this exact problem has been raised recently on LQ in 
> the "SBo scripts not building on current" thread. Therefore first 
> question regards whether you're seeing this problem in 
> Slackware-stable or -current?
>
> Unfortunately I have tried all combinations (I think) of build flags 
> in clean -stable & -current VMs and have not been able to replicate 
> the problem. I just built it again now without incident in -stable 
> using IMAGING=yes and MPI=yes flags. Therefore the next question is 
> whether you're building in a VM or normal environment. If the latter, 
> how clean is it?
>
>
> chris
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
I'm running on stable (15.0 64bit)

Thanks for looking at this Chris. I have managed to get VTK to build now.
My solution was to uninstall the existing (older) version of VTK before 
creating the newer package. If someone wants to confirm this as a 
repeatable solution then it may be worth adding a comment to that effect 
to the readme.
regards, Tim