Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. [Solved] Qt 4.8.5 QNetwork/SSL Compile Errors
Forum Updated to NodeBB v4.3 + New Features

[Solved] Qt 4.8.5 QNetwork/SSL Compile Errors

Scheduled Pinned Locked Moved Mobile and Embedded
5 Posts 2 Posters 2.4k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D Offline
    D Offline
    Donny3000
    wrote on last edited by
    #1

    Hello All,

    I'm trying to compile Qt4.8.5 embedded linux from source with OpenSSL enabled for QNetwork, but I keep running into these Ssl errors (pastebin "link":http://pastebin.com/ZazbPs2S since the Ssl errors are lengthy). I'm basically configuring Qt fro an ARM Cortex A-8 platform. This is the output of my configure results:

    bq. Building on: qws/linux-x86_64-g++
    Building for: linux-arm-gnueabihf-g++
    Architecture: arm
    Host architecture: x86_64
    Build .................. libs examples demos docs translations
    Configuration .......... cross_compile release embedded largefile stl neon minimal-config small-config medium-config large-config full-config no-pkg-config accessibility shared embedded reduce_exports ipv6 clock-gettime clock-monotonic mremap getaddrinfo ipv6ifname getifaddrs inotify png freetype zlib nis openssl concurrent xmlpatterns multimedia audio-backend svg script scripttools declarative release
    Debug .................. no
    Qt 3 compatibility ..... no
    QtDBus module .......... no
    QtConcurrent code ...... yes
    QtGui module ........... yes
    QtScript module ........ yes
    QtScriptTools module ... yes
    QtXmlPatterns module ... yes
    Phonon module .......... no
    Multimedia module ...... auto
    SVG module ............. yes
    WebKit module .......... no
    JavaScriptCore JIT ..... To be decided by JavaScriptCore
    Declarative module ..... yes
    Declarative debugging ...yes
    Support for S60 ........ no
    Symbian DEF files ...... no
    STL support ............ yes
    PCH support ............ no
    MMX/3DNOW/SSE/SSE2/SSE3. no/no/no/no/no
    SSSE3/SSE4.1/SSE4.2..... no/no/no
    AVX..................... no
    iWMMXt support ......... no
    NEON support ........... yes
    IPv6 support ........... yes
    IPv6 ifname support .... yes
    getaddrinfo support .... yes
    getifaddrs support ..... yes
    Accessibility .......... yes
    NIS support ............ yes
    CUPS support ........... no
    Iconv support .......... no
    Glib support ........... no
    GStreamer support ...... no
    PulseAudio support ..... no
    Large File support ..... yes
    GIF support ............ plugin
    TIFF support ........... plugin (qt)
    JPEG support ........... plugin (qt)
    PNG support ............ yes (qt)
    MNG support ............ plugin (qt)
    zlib support ........... yes
    Session management ..... no
    Embedded support ....... arm
    Freetype2 support ...... yes
    Graphics (qt) .......... linuxfb multiscreen linuxfb transformed
    Graphics (plugin) ......
    Decorations (qt) ....... styled windows default
    Decorations (plugin) ...
    Keyboard driver (qt) ... tty tty linuxinput
    Keyboard driver (plugin) ..
    Mouse driver (qt) ...... pc linuxtp pc linuxtp linuxinput
    Mouse driver (plugin) ..
    OpenGL support ......... no
    OpenVG support ......... no
    SQLite support ......... plugin (qt)
    OpenSSL support ........ yes (run-time)
    Alsa support ........... no
    ICD support ............ no
    libICU support ......... no
    Use system proxies ..... no

    Does anyone know what might be going wrong? I'm at loss right now because I done everything that I know of to try and resolve this issue.

    1 Reply Last reply
    0
    • SGaistS Offline
      SGaistS Offline
      SGaist
      Lifetime Qt Champion
      wrote on last edited by
      #2

      Hi and welcome to devnet,

      Might be a silly question, but do you have openssl for ARM and are you sure it was detected properly ?

      Interested in AI ? www.idiap.ch
      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

      1 Reply Last reply
      0
      • D Offline
        D Offline
        Donny3000
        wrote on last edited by
        #3

        Thanks for your respose SGaist. I do have OpenSSL for ARM cross-compiled and I believe it is being detected correctly. If I go into config.tests/unix/openssl from the source root folder I see that the openssl configure test program has indeed been built, although it's built for ARM, not my x86_64 host (which I believe is to be expected). I believe this is why OpenSSL support.......yes (run-time) is present in the configuration summary.

        The first time I compiled the source, I didn't have OpenSSL and the Qt configuration summary didn't mention OpenSSL Support and Qt compiled successfully. But, now that I have OpenSSL compiled for ARM and it appears that Qt has found OpenSSL (per the configuration summary), Qt doesn't seem to build.

        1 Reply Last reply
        0
        • D Offline
          D Offline
          Donny3000
          wrote on last edited by
          #4

          Well, after performing a complete clean (make uninstall, rm -rf of install directories and Qt source), the build successfully complied the QNetwork library (with OpenSSL support), in addition to the rest of the Qt libraries. So, my problem has been solved. I guess some lingering configurations was causing my problems. Thanks again SGaist for chiming in to assist with my issue.

          1 Reply Last reply
          0
          • SGaistS Offline
            SGaistS Offline
            SGaist
            Lifetime Qt Champion
            wrote on last edited by
            #5

            You're welcome !

            That's one of the rule when reconfiguring Qt: you have to clean before calling configure. If you use out of source build you can simply delete what's inside the folder.

            Since you have it working now, please update the thread prepending [solved] so other forum users may know a solution has been found :)

            Interested in AI ? www.idiap.ch
            Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

            1 Reply Last reply
            0

            • Login

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • Users
            • Groups
            • Search
            • Get Qt Extensions
            • Unsolved