I have discovered that squiddio creates a core dump at start when it's activated inside the last OpenCPN-5.14.0...
You perhaps know that for years I have been creating and maintaining rpms for OpenCPN and some of its plugins, allowing to use it without needing flatpak.
I have rebuilt all the stuff for the next coming Mageia10 and discovered this problem when testing it
Nota Bene
as I already mentioned here #162
Like for other plugins : One line needs to be added (#include <cstdint>) in opencpn-libs/api-18/ocpn-plugin.h for building it with GCC 15...
the use of opencpn-libs/api-20/ocpn-plugin.h doesn't need this
I have had a core dump when I launched OpenCpn-5.14.0 with all its plugins activated =>So I uninstalled all of their rpms and installed them one by one.... and discovered that Squiddio was the culprit !!!
Something to know :
Squiddio and all the other plugins don't induce a core dump with OpenCPN-5.12.4 ....
when they are built with the same system basis that I used to package OpenCPN-5.12.4 and the last OpenCPN-5.14.0...
That seems to be strictly a compatibility problem with OpenCPN-5.14.0.
I have discovered that squiddio creates a core dump at start when it's activated inside the last OpenCPN-5.14.0...
You perhaps know that for years I have been creating and maintaining rpms for OpenCPN and some of its plugins, allowing to use it without needing flatpak.
I have rebuilt all the stuff for the next coming Mageia10 and discovered this problem when testing it
Nota Bene
as I already mentioned here #162
Like for other plugins : One line needs to be added (
#include <cstdint>) in opencpn-libs/api-18/ocpn-plugin.h for building it with GCC 15...the use of opencpn-libs/api-20/ocpn-plugin.h doesn't need this
I have had a core dump when I launched OpenCpn-5.14.0 with all its plugins activated =>So I uninstalled all of their rpms and installed them one by one.... and discovered that Squiddio was the culprit !!!
Something to know :
Squiddio and all the other plugins don't induce a core dump with OpenCPN-5.12.4 ....
when they are built with the same system basis that I used to package OpenCPN-5.12.4 and the last OpenCPN-5.14.0...
That seems to be strictly a compatibility problem with OpenCPN-5.14.0.