mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Matthias Klein" <matthias.klein@optimeas.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] qt4 - openssl support: symbol lookup error: undefined symbol: _ZN10QSslSocket11supportsSslEv
Date: Fri, 27 Sep 2013 12:42:48 +0000	[thread overview]
Message-ID: <em16ac131c-9713-4f0c-9790-915b3a467d5b@nb-mak> (raw)

Hello,

in a working BSP project I need SSL support in QT4. Therefore I have 
enabled PTXCONF_QT4_OPENSSL.
I have rebuiled QT4 without problems by clean & targetinstall.

In a small test application I tried to verify SSL:

#include <QSslSocket>
     if(QSslSocket::supportsSsl())
...

The app compiles fine, but when I run them on the target I get:

./sslTest: symbol lookup error: ./sslTest: undefined symbol: 
_ZN10QSslSocket11supportsSslEv


I tried to verify that the function is in the Network library of Qt:

$ arm-cortexa8-linux-gnueabihf-objdump -d 
platform-tx53/root/usr/lib/libQtNetwork.so | grep supportsSsl
    2c428: eb0215f4  bl b1c00 <_ZN10QSslSocket11supportsSslEv>
    abea8: eb001754  bl b1c00 <_ZN10QSslSocket11supportsSslEv>
    afe58: eb000768  bl b1c00 <_ZN10QSslSocket11supportsSslEv>
    afed8: eb000748  bl b1c00 <_ZN10QSslSocket11supportsSslEv>
    b07cc: eb00050b  bl b1c00 <_ZN10QSslSocket11supportsSslEv>
For me it looks OK.


Then I did a complete ptxdist distclean & go cycle for safety, but the 
result is the same ...
Besides SSL QT4 runs fine on the target. (The BSP use ptxdist-2013.09.0 
& OSELAS Toolchain 2012.12.1 arm-cortexa8-linux-gnueabihf)


Did I something wrong ?
Any tips what I can do / investigate ?


Best regards,

Matthias


-- 
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2013-09-27 12:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-27 12:42 Matthias Klein [this message]
2013-09-27 13:14 ` Jürgen Beisert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=em16ac131c-9713-4f0c-9790-915b3a467d5b@nb-mak \
    --to=matthias.klein@optimeas.de \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox