Results 1 to 12 of 12

Thread: ./configure cant find qt

  1. #1
    Registered User
    Join Date
    Feb 2003
    Posts
    4

    Angry ./configure cant find qt

    i did a fresh install with showeq 4.3.5 and used qt 3.0.5...everything compiled fine. Now i moved over to 4.3.6 and i export everything properly, and do everything as i'm told in the things i've read (followed the INSTALL.newbies to a T) and when ./configure gets to qt, it says it cant find qt..
    here's everything i did:

    [root@localhost rage]# locate qt|grep 3.0.5
    /usr/lib/qt-3.0.5
    /usr/lib/qt-3.0.5/bin
    /usr/lib/qt-3.0.5/bin/qtconfig
    /usr/lib/qt-3.0.5/lib
    /usr/lib/qt-3.0.5/lib/libeditor.so.1.0
    /usr/lib/qt-3.0.5/lib/libeditor.so.1
    /usr/lib/qt-3.0.5/lib/libeditor.so.1.0.0
    /usr/lib/qt-3.0.5/lib/libqt-mt.so.3
    /usr/lib/qt-3.0.5/lib/libqt-mt.so.3.0
    /usr/lib/qt-3.0.5/lib/libqt-mt.so.3.0.5
    /usr/lib/qt-3.0.5/lib/libqt.so.3
    /usr/lib/qt-3.0.5/lib/libqt.so.3.0
    /usr/lib/qt-3.0.5/lib/libqt.so.3.0.5
    /usr/lib/qt-3.0.5/lib/libqui.so.1
    /usr/lib/qt-3.0.5/lib/libqui.so.1.0
    /usr/lib/qt-3.0.5/lib/libqui.so.1.0.0
    /usr/lib/qt-3.0.5/plugins
    /usr/lib/qt-3.0.5/plugins/styles
    /usr/lib/qt-3.0.5/plugins/styles/bluecurve.la
    /usr/lib/qt-3.0.5/plugins/styles/bluecurve.so
    /usr/lib/qt-3.0.5/etc
    /usr/lib/qt-3.0.5/etc/settings
    /usr/lib/qt-3.0.5/etc/settings/kstylerc
    /usr/lib/qt-3.0.5/etc/settings/qtrc
    /usr/share/doc/qt-3.0.5
    /usr/share/doc/qt-3.0.5/LICENSE.QPL
    /usr/share/doc/qt-3.0.5/FAQ
    /usr/share/doc/qt-3.0.5/README.QT
    /usr/share/doc/qt-3.0.5/README
    /usr/share/doc/qt-3.0.5/changes-3.0.5
    /home/rage/qt-x11-free-3.1.1/examples/demo/qasteroids/sprites/rock3/rock30005.png
    /home/rage/qt-x11-free-3.1.1/examples/demo/qasteroids/sprites/rock3/rock30015.png
    /home/rage/qt-x11-free-3.1.1/examples/demo/qasteroids/sprites/rock3/rock30025.png
    [root@localhost rage]# cvs -dserver:[email protected]:/cvsroot/seq login
    Logging in to server:[email protected]:2401/cvsroot/seq
    CVS password:
    [root@localhost rage]# cvs -z3 -dserver:[email protected]:/cvsroot/seq co showeq
    ? showeq/autom4te-2.53.cache
    cvs server: Updating showeq
    cvs server: Updating showeq/conf
    cvs server: Updating showeq/doc
    cvs server: Updating showeq/maps
    cvs server: Updating showeq/src
    [root@localhost rage]# cvs -dserver:[email protected]:/cvsroot/seq logout
    Logging out of server:[email protected]:2401/cvsroot/seq
    [root@localhost rage]# cd showeq
    [root@localhost showeq]# gcc
    gcc: no input files
    [root@localhost showeq]# g++
    g++: no input files
    [root@localhost showeq]# gcc -v
    Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2/specs
    Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --host=i386-redhat-linux --with-system-zlib --enable-__cxa_atexit
    Thread model: posix
    gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)
    [root@localhost showeq]# g++ -v
    Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2/specs
    Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --host=i386-redhat-linux --with-system-zlib --enable-__cxa_atexit
    Thread model: posix
    gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)
    [root@localhost showeq]# export CC=gcc
    [root@localhost showeq]# export CXX=g++
    [root@localhost showeq]# export QTDIR=/usr/lib/qt-3.0.5
    [root@localhost showeq]# make -f Makefile.dist
    Adding libtool support...................................... done!
    Generating aclocal.m4 from configure.in and acinclude.m4.... done!

    Checking Autoheader version................................. done!
    >> Using Autoheader version................................. Autoconf)
    Roland

    Free
    free
    even!

    Generating configure template (config.h).................... done!
    Generating Makefile.in from Makefile.am..................... done!

    Checking Autoconf version................................... done!
    >> Using Autoconf version................................... Autoconf)
    David

    Free
    free
    even!

    Finalizing Autoconf script (configure)...................... done!
    Releasing temporary file handles............................ done!


    ******************************************
    Success! Please type the following:

    ./configure && make


    This will configure and compile ShowEQ...

    If you are installing ShowEQ for the first
    time, be sure to add '&& make install' to
    the end of the compile process...
    ******************************************

    [root@localhost showeq]# ./configure && make
    checking build system type... i686-pc-linux-gnu
    checking host system type... i686-pc-linux-gnu
    checking target system type... i686-pc-linux-gnu
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    /home/rage/showeq/missing: Unknown `--run' option
    Try `/home/rage/showeq/missing --help' for more information
    configure: WARNING: `missing' script is too old or missing
    checking for gawk... gawk
    checking whether make sets ${MAKE}... yes
    checking whether to enable maintainer-specific portions of Makefiles... no
    checking for gcc... gcc
    checking for g++... g++
    checking for supported compiler version... checking for style of include used by make... GNU
    checking for C++ compiler default output... a.out
    checking whether the C++ compiler works... yes
    checking whether we are cross compiling... no
    checking for suffix of executables...
    checking for suffix of object files... o
    checking whether we are using the GNU C++ compiler... yes
    checking whether g++ accepts -g... yes
    checking dependency style of g++... gcc3
    yes
    checking for gcc... gcc
    checking whether we are using the GNU C compiler... yes
    checking whether gcc accepts -g... yes
    checking dependency style of gcc... gcc3
    checking whether we are using the GNU C++ compiler... (cached) yes
    checking whether g++ accepts -g... (cached) yes
    checking dependency style of g++... (cached) gcc3
    checking how to run the C preprocessor... gcc -E
    checking for gcc option to accept ANSI C... none needed
    checking for an ANSI C-conforming const... yes
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether ln -s works... yes
    checking whether make sets ${MAKE}... (cached) yes
    checking for ld used by GCC... /usr/bin/ld
    checking if the linker (/usr/bin/ld) is GNU ld... yes
    checking for /usr/bin/ld option to reload object files... -r
    checking for BSD-compatible nm... /usr/bin/nm -B
    checking how to recognise dependant libraries... pass_all
    checking command to parse /usr/bin/nm -B output... ok
    checking for ANSI C header files... yes
    checking for sys/types.h... yes
    checking for sys/stat.h... yes
    checking for stdlib.h... yes
    checking for string.h... yes
    checking for memory.h... yes
    checking for strings.h... yes
    checking for inttypes.h... yes
    checking for stdint.h... yes
    checking for unistd.h... yes
    checking dlfcn.h usability... yes
    checking dlfcn.h presence... yes
    checking for dlfcn.h... yes
    checking for ranlib... ranlib
    checking for strip... strip
    checking for objdir... .libs
    checking for gcc option to produce PIC... -fPIC
    checking if gcc PIC flag -fPIC works... yes
    checking if gcc static flag -static works... yes
    checking if gcc supports -c -o file.o... yes
    checking if gcc supports -c -o file.lo... yes
    checking if gcc supports -fno-rtti -fno-exceptions... yes
    checking whether the linker (/usr/bin/ld) supports shared libraries... yes
    checking how to hardcode library paths into programs... immediate
    checking whether stripping libraries is possible... yes
    checking dynamic linker characteristics... GNU/Linux ld.so
    checking if libtool supports shared libraries... yes
    checking whether to build shared libraries... yes
    checking whether to build static libraries... yes
    checking whether -lc should be explicitly linked in... no
    creating libtool
    checking for supported libc version... yes
    checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
    checking for IceConnectionNumber in -lICE... yes
    checking for libXext... yes
    checking for extra includes... no
    checking for extra libs... no
    checking for libz... -lz
    checking for libpng... -lpng -lz -lm
    checking for Qt... no
    >> Unable to locate your Qt includes...
    configure: error: Please verify your Qt devel install!
    [root@localhost showeq]#

  2. #2
    Registered User
    Join Date
    Dec 2001
    Posts
    411
    fucking a


    install the QT dev packages .........


    and use the search button, its not like this issue hasnt been answered before. Heck, iv'e had 8 pints of shiner bock in the past 2 hours, and i remember the answer, it cant be that hard to find.
    casey AT trifocus DOT net

  3. #3
    Registered User
    Join Date
    Feb 2003
    Posts
    4
    I couldn't find it...and wouldnt they be needed to install 4.3.5?

  4. #4
    Registered User
    Join Date
    Dec 2001
    Posts
    411
    Originally posted by Ragecloak
    I couldn't find it...and wouldnt they be needed to install 4.3.5?
    it? the qt dev packages?

    no, they are not needed to install showeq.
    yes, they are needed to compile showeq, and notice thats where you are having the problem. i dont make this stuff up for my personal amusement.

  5. #5
    Registered User
    Join Date
    Dec 2001
    Posts
    752
    have you read this ?

    http://seq.sourceforge.net/showthrea...hlight=qt3.0.5

    i use to configure

    ./configure --with-qt-dir=/usr/lib/qt-3.0.5

    ... dont make casey angry
    -- Lord Crush

    Greater Faydark has to be cleaned from all Elves !

    This is a HOTKEY !!!

  6. #6
    Registered User
    Join Date
    Feb 2003
    Posts
    4
    it? the qt dev packages?
    no, a post describing what my problem is...everything should be installed..
    yes, they are needed to compile showeq, and notice thats where you are having the problem.
    i meant compile (you probably knew that too, considering you responded to that in the next line), thus, i had them for the compile of my last version of showeq, correct?
    i dont make this stuff up for my personal amusement.
    I never said you did, ass.

  7. #7
    Registered User
    Join Date
    Feb 2003
    Posts
    16
    I had a similar problem and found that it was simply that my QTDIR environmental variable was pointing at the old version of QT, even though I had 3.0.5 installed. a quick change to that variable fixed the problem, so you may want to check this if you haven't already.



    and yes, actually they do make up those brutal responses for their own amusement. if thats not the case than there are some seriously troubled people obsessed with writing horrible hurtful things here instead of just ignoring posts that annoy them or writing simple fast answers.
    Yet another useless response from the know it alls that took longer to write than it would have taken to just answer the question.

  8. #8
    Registered User
    Join Date
    Dec 2001
    Posts
    752
    Surak,

    1st if you use "--with-qt-dir" ... you don't need the $QTDIR Variable - btw i got the tip about one year ago from casey

    2nd i have seen so much posts here that ask questions that are answered 2 posts below or you get answer if you type ONE word into search...
    I understand and i agree to flaming at this point ... i dont wan't to type the same answer x times cause of people are to lazy to use search or read.

    I know enough people from work who rather take the phone and call before they switch on their brain ...

    No flame ... (not now )
    -- Lord Crush

    Greater Faydark has to be cleaned from all Elves !

    This is a HOTKEY !!!

  9. #9
    Registered User
    Join Date
    Oct 2002
    Posts
    67
    If its a fresh install of RH8, you shouldn't have to export any of the QT variables. Its all assumed in RH8(and if you installed it properly, should work just fine) Try ommitting the variables and recompile. Also, make sure you've installed the Devel packages for QT... I made the mistake of leaving it out on my first install, which isn't a problem, because you can install them later with no problem.
    Usually I post my character here...but uh...yeah...

  10. #10
    Registered User
    Join Date
    Feb 2003
    Posts
    2
    usually we get rid of this "chaing qt dir" and stuff by making a sim link. after compiling qt in /usr/lib/qt-x.xx,
    Code:
    cd /usr/lib/
    ln -s qt-x.xx qt
    then just put /usr/lib/qt/lib in to ldconfig.conf instead of the non-symlink dir

  11. #11
    Registered User
    Join Date
    Dec 2001
    Posts
    752
    /nod,

    but my KDE dont runs with this QT-Lib ... dont want to change KDE :P
    -- Lord Crush

    Greater Faydark has to be cleaned from all Elves !

    This is a HOTKEY !!!

  12. #12
    Registered User
    Join Date
    Feb 2003
    Posts
    2
    kde 3.1 is a big step up, assuming you're using 3. And it only takes like 2 days to compile on a 1.8 GHz laptop!

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

You may post new threads
You may post replies
You may post attachments
You may edit your posts
HTML code is Off
vB code is On
Smilies are On
[IMG] code is On