At a guess, and not having looked at the code or logs, I would say it’s either a virtual destructor defined in a header file (that can cause problems with the vtable not being generated by any compilation unit) or it has been built with -fvisibility=hidden and the class is not marked with visibility(“default”) and so members are not exported from the library
Michael
On Tue, 28 Nov 2017, at 10:35 PM, Michael Cullen wrote:
At a guess, and not having looked at the code or logs, I would say it’s either a virtual destructor defined in a header file (that can cause problems with the vtable not being generated by any compilation unit) or it has been built with -fvisibility=hidden and the class is not marked with visibility(“default”) and so members are not exported from the libraryMichaelOn Tue, 28 Nov 2017, at 09:17 PM, Martin Gansser wrote:> Maybe someone can tell me which forum I can contact to fix this error?> _______________________________________________> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
