Page MenuHomePhabricator

Build tree version of MitkWorkbench crashes twice before eventually starting on Ubuntu with GCC
Closed, ResolvedPublic

Description

NOTE: Clang works just fine regarding to this issue.

bin/MitkWorkbench --BlueBerry.clean: org.blueberry.core.expressions fails to start because of missing symbol berry::SmartPointer<Expression> berry::ElementHandler::Create(ExpressionConverter* converter, Poco::XML::Element* element). However, this symbol seems to be exported when checking with readelf -Ws and it compares well to the Clang version.

bin/MitkWorkbench: We have some loose dependencies to Qt5PrintSupport that GCC 7.3 doesn't handle well when linking. Turns out that some dummy code right in those plugins that uses this library directly is a workaround.

There is also an error indicating that the system version of Qt is mixed with the actual version of Qt used when building MITK. This error vanishes into thin air when starting the Workbench again.

Event Timeline

kislinsk created this task.

There's more going on on a clean Ubuntu 18.04 VM with GCC and starting MitkWorkbench for the first time. Basically no plugin is able to start because of broken linkage to libQt5Svg. That's probably a hot candidate for the version mismatch error on systems with a system version of that lib.

Uh, I'm carefully optimistic that this really fixed the start of the MitkWorkbench. :-) Will test on Monday at another Ubuntu machine that has/had the Qt version mismatch error.

Okay, all the Qt-related startup errors are fixed. But, on some PCs there is still the following one-time error even without --BlueBerry.clean:

org.blueberry.core.expressions fails to start because of missing symbol berry::SmartPointer<Expression> berry::ElementHandler::Create(ExpressionConverter* converter, Poco::XML::Element* element)