PDA

View Full Version : QT error?



KenJF
02-28-2014, 10:39 AM
ok. i am not usually one to start a whole thread on my problems i have with anything. but at this point i am stumped. i have looked up everything i can think of. installed every QT thing i could find. and tried so many pieces of code. its all a blur to me now.

Here is what im getting when i do ./configure.

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
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
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 whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
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 for gcc option to accept ISO C89... none needed
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 an ANSI C-conforming const... yes
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... 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 for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC 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.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for supported libc version... yes
checking for X... libraries , headers
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!



Im running 32bit Ubuntu 13.10 on a thinkpad r61i

BlueAdept
02-28-2014, 08:09 PM
What version of QT? I believe SEQ requires v4.xx, I think Ubuntu has v5. (Dont quote me. It has been a quite a while since I had SEQ running. I could be wrong but it is a suggestion.).

Also make sure your qt devel is installed.

fransick
03-01-2014, 04:40 AM
I am using QT 3.3 as my understanding is that SEQ will not work reliably with anything 4 or above? I recall a while back someone beginning work on porting code to QT4 but it never came to fruition. I could be completely off base but i do know it works on QT 3 without issue.

Razzle
03-03-2014, 02:33 PM
If I recall, ubuntu 13 no longer has support for qt3. Seq doesnt support qt4 or qt5.

Razzle

BlueAdept
03-04-2014, 06:12 PM
You can probably install QT3 though. I used to have to do that years and years ago when a previous version of QT wasnt supported in Redhat.

CentOS installs and works right out of the box (at least it used to. I havent done it in a long time).

Spanners
03-14-2014, 03:31 AM
It took me quite a while to track down the qt3 installs for the raspberry pi, if you seek you will surely find (eventually) .

Android8675
03-30-2014, 12:55 PM
Similar issue, using Debian7.4, I compiled and installed QT 3.3.8, when I run ./configure I get:checking for Qt... yes>> Found version.: 3.3.8>>> Headers....: /usr/local/qt/include>>>> Libraries...: Unable to locate?!?configure: error: Please verify your Qt lib install!Running a barebones system with Fluxbox, can't even figure out how to cut/Paste, but let me know what I can send to help, if anything.-A.

Android8675
03-30-2014, 04:44 PM
Disregard previous message,
QT 3.3.8 wasn't compiling (Debian 7.4, Wheezy), but I found out that pkgs.org has a package called qt3-tools-dev compatible with Wheezy.
Installed that, and ShowEQ ./configure worked just fine (though it could not find the QT3 docs, even though I installed a QT3-doc package as well, but didn't seem to have an issue).
At any rate, Maybe this will help someone else who comes along and wants to get ShowEQ up and running in Debian Wheezy
....Just finished building, is loading, now to see if the offset is correct and what not... :)