Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. [solved] Building problems while trying to build Qt 4.7.3 on a machine that has installed Qt 4.4.3
Forum Updated to NodeBB v4.3 + New Features

[solved] Building problems while trying to build Qt 4.7.3 on a machine that has installed Qt 4.4.3

Scheduled Pinned Locked Moved Installation and Deployment
3 Posts 2 Posters 1.9k 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.
  • M Offline
    M Offline
    markus.liebe
    wrote on last edited by
    #1

    Hi there,

    I am trying to build Qt 4.7.3 on a linux machine that comes with a installed Qt 4.4.3.
    In the beginning of t he build process qmake reads all the .pro files in source dir and creates the corresponding Makefiles.
    Each of the created Makefiles has a line like:

    @LIBS = $(SUBLIBS) -L/usr/lib64 -L/home/user/rpmbuild/BUILD/qt-everywhere-opensource-src-4.7.3/lib -lQtCore -L/usr/lib64 -lz -lm -pthread -L/opt/gnome/lib64 -lgthread-2.0 -lglib-2.0 -lrt -ldl -lpthread @

    The problem is the first occurence of "-L/usr/lib64" which has precedence over "-L/home/user/rpmbuild/BUILD/qt-everywhere-opensource-src-4.7.3/lib"
    As a consequence the wrong QtCore is used (the Qt 4.4.3 one out of /usr/lib64), which results in a linker error.

    In my opinion qmake should not put the /usr/lib64 path in front of the other library path.

    Do you have any hints on how to get that right?
    Is this a bug in qmake?

    Regards,
    Markus

    1 Reply Last reply
    0
    • G Offline
      G Offline
      goetz
      wrote on last edited by
      #2

      This must have been added from somewhere else. I tried a configure run on an older kubuntu box with Qt 4.4.1 libs in /usr/lib64, I do not have that path in the LIBS variable. Maybe it sneaked in by some other dependency which is installed there?

      http://www.catb.org/~esr/faqs/smart-questions.html

      1 Reply Last reply
      0
      • M Offline
        M Offline
        markus.liebe
        wrote on last edited by
        #3

        Thanks for the hint Volker.
        I had a closer look into the .spec file of the rpm that I am using and behold:
        there is a line passing several extra parameters to the configure call:

        -- ok now the third try to get that following line into the post. It was parsed away by the forum.

        The line contains:
        @define common_options -L%libdir@

        I changed that line to my needs and the issue is solved now.

        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