[Qgis-developer] Crash of QGIS 2.4 built on RHEL 6 with Qt 5.3

[Dave Johansen]

Yep, QWT and QWT-Polar were the offending libraries. Once I built a Qt5
version and used this, QGIS 2.4 loaded up just fine on RHEL 6. Thanks for
the help,
Dave

On Mon, Sep 8, 2014 at 3:52 AM, Matthias Kuhn <matthias.kuhn at gmx.ch> wrote:

> Hi Dave,
>
> Maybe it could be QWT (and QWT-Polar) which are linked against Qt4? You
> will probably have to recompile such dependencies as well.
>
> On Fri 05 Sep 2014 08:24:33 PM CEST, Dave Johansen wrote:
>
>> On Thu, Sep 4, 2014 at 11:38 PM, Matthias Kuhn <matthias.kuhn at gmx.ch
>> <mailto:matthias.kuhn at gmx.ch>> wrote:
>>
>>     Hi Dave
>>
>>     there is still Qt 4 involved (partially?) as the 4 in the end of
>>     this line indicates:
>>
>>     #10 0x00007ffff3e24ce6 in __do_global_ctors_aux () from
>>     /usr/lib64/libQtCore.so.4
>>
>>     Did you clean the build directory after the build attempts for master?
>>
>>
>> I just did a complete clean build just to be sure and it had the same
>> crash. The same crash happened. Here's the output from ldd grepped for qt:
>>
>>     libQt5Sql.so.5 => /usr/lib64/libQt5Sql.so.5 (0x000000357c400000)
>>     libQt5WebKit.so.5 => /usr/lib64/libQt5WebKit.so.5 (0x0000003585200000)
>>     libQt5WebKitWidgets.so.5 => /usr/lib64/libQt5WebKitWidgets.so.5
>> (0x0000003580000000)
>>     libqgis_core.so.2.4.0 =>
>> /home/dlj/projects/qgis-qt5/build/../install/lib/libqgis_core.so.2.4.0
>> (0x00007faf1211c000)
>>     libqgis_gui.so.2.4.0 =>
>> /home/dlj/projects/qgis-qt5/build/../install/lib/libqgis_gui.so.2.4.0
>> (0x00007faf11a01000)
>>     libqgis_analysis.so.2.4.0 =>
>> /home/dlj/projects/qgis-qt5/build/../install/lib/libqgis_
>> analysis.so.2.4.0
>> (0x00007faf11772000)
>>     libQt5Quick.so.5 => /usr/lib64/libQt5Quick.so.5 (0x000000357c800000)
>>     libQt5Qml.so.5 => /usr/lib64/libQt5Qml.so.5 (0x000000357b200000)
>>     libQt5OpenGL.so.5 => /usr/lib64/libQt5OpenGL.so.5 (0x000000357f400000)
>>     libQt5Sensors.so.5 => /usr/lib64/libQt5Sensors.so.5
>> (0x000000357fc00000)
>>     libQt5Network.so.5 => /usr/lib64/libQt5Network.so.5
>> (0x0000003579e00000)
>>     libQt5PrintSupport.so.5 => /usr/lib64/libQt5PrintSupport.so.5
>> (0x000000357ee00000)
>>     libQt5Positioning.so.5 => /usr/lib64/libQt5Positioning.so.5
>> (0x000000357f800000)
>>     libQt5Xml.so.5 => /usr/lib64/libQt5Xml.so.5 (0x000000357a200000)
>>     libQt5Concurrent.so.5 => /usr/lib64/libQt5Concurrent.so.5
>> (0x00007faf1133c000)
>>     libQt5Svg.so.5 => /usr/lib64/libQt5Svg.so.5 (0x00007faf110eb000)
>>     libQt5Widgets.so.5 => /usr/lib64/libQt5Widgets.so.5
>> (0x000000357ba00000)
>>     libQt5Gui.so.5 => /usr/lib64/libQt5Gui.so.5 (0x000000357aa00000)
>>     libQt5Core.so.5 => /usr/lib64/libQt5Core.so.5 (0x0000003578a00000)
>>     libQtSvg.so.4 => /usr/lib64/libQtSvg.so.4 (0x0000003582200000)
>>     libQtGui.so.4 => /usr/lib64/libQtGui.so.4 (0x00007faf0fda5000)
>>     libQtCore.so.4 => /usr/lib64/libQtCore.so.4 (0x00007faf0f941000)
>>
>> So it looks like you already pointed out that the Qt4 libraries are
>> being linked in as well for some reason. Any ideas on what I should do
>> to run down where this issue is coming from?
>>
>>     For your other question (lrelease-qt5) you can revert this commit:
>>     9c6f1698fcb3df758f024fad99ed65__06d6a38e0d
>>
>>     I guess I'll have to figure out another approach to handle this
>>     suffix than just deleting it like this commit does.
>>
>>
>> I reverted that commit and it built without me specifying the path to
>> lrelease-qt5.
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20140908/e418d49d/attachment.html>