Find the answer to your Linux question:
Page 2 of 2 FirstFirst 1 2
Results 11 to 16 of 16
OK, here's a possible solution: http://lists.debian.org/debian-devel.../msg01330.html To summarise, the program you're compiling might be looking in '/blahblah/qt' for the headers whereas they are in fact installed in '/blahblah/qt3.3' or somesuch. ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #11
    Linux User
    Join Date
    Aug 2005
    Location
    Peterborough, UK
    Posts
    379

    OK, here's a possible solution: http://lists.debian.org/debian-devel.../msg01330.html

    To summarise, the program you're compiling might be looking in '/blahblah/qt' for the headers whereas they are in fact installed in '/blahblah/qt3.3' or somesuch. 'blahblah' may be /usr/include/ or /usr/lib/ (or lib64 if using x86_64).

    Try creating symbolic links of the appropriate folders and attempt the configure and make again.
    \"I am, after all,\" said Pooh, \"a bear of very little brain.\"
    MY PC: Athlon XP64 3000+ on a Asus K8V-X mobo w/1GB of non-descript RAM. AGP - GeForce 2 MX400. PCI - Creative Live! 5.1 soundcard. 140 GB and 120 GB SATA WD drives.

  2. #12
    Just Joined!
    Join Date
    Jan 2005
    Posts
    66
    Hi Old BLoke,

    I made a symbolic link to /usr/lib/qt-3.3 in the same folder that the configure file resides. This made the qt error go away. The output is now:
    [root@localhost superkaramba-0.37-RC1]# ./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 for -p flag to install... yes
    checking whether build environment is sane... yes
    checking for gawk... gawk
    checking whether make sets $(MAKE)... yes
    checking for kde-config... /usr/bin/kde-config
    checking where to install... /usr (as returned by kde-config)
    checking for style of include used by make... GNU
    checking for gcc... gcc
    checking for C compiler default output file name... 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 gcc accepts -g... yes
    checking for gcc option to accept ANSI C... none needed
    checking dependency style of gcc... gcc3
    checking how to run the C preprocessor... gcc -E
    checking for g++... g++
    checking whether we are using the GNU C++ compiler... yes
    checking whether g++ accepts -g... yes
    checking dependency style of g++... gcc3
    checking whether gcc is blacklisted... no
    checking whether g++ supports -Wmissing-format-attribute... yes
    checking whether gcc supports -Wmissing-format-attribute... yes
    checking whether g++ supports -Wundef... yes
    checking whether g++ supports -Wno-long-long... yes
    checking whether g++ supports -Wnon-virtual-dtor... yes
    checking whether g++ supports -fno-exceptions... yes
    checking whether g++ supports -fno-check-new... yes
    checking whether g++ supports -fno-common... yes
    checking whether g++ supports -fexceptions... yes
    checking how to run the C++ preprocessor... g++ -E
    checking whether g++ supports -O0... yes
    checking whether g++ supports -Wl,--no-undefined... yes
    checking whether g++ supports -Wl,--allow-shlib-undefined... yes
    not using lib directory suffix
    checking for a sed that does not truncate output... /bin/sed
    checking for egrep... grep -E
    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 whether ln -s works... yes
    checking how to recognise dependent libraries... pass_all
    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 g77... no
    checking for f77... no
    checking for xlf... no
    checking for frt... no
    checking for pgf77... no
    checking for fort77... no
    checking for fl32... no
    checking for af77... no
    checking for f90... no
    checking for xlf90... no
    checking for pgf90... no
    checking for epcf90... no
    checking for f95... f95
    checking whether we are using the GNU Fortran 77 compiler... yes
    checking whether f95 accepts -g... yes
    checking the maximum length of command line arguments... 32768
    checking command to parse /usr/bin/nm -B output from gcc object... ok
    checking for objdir... .libs
    checking for ar... ar
    checking for ranlib... ranlib
    checking for strip... strip
    checking if gcc static flag works... yes
    checking if gcc supports -fno-rtti -fno-exceptions... no
    checking for gcc option to produce PIC... -fPIC
    checking if gcc PIC flag -fPIC works... yes
    checking if gcc supports -c -o file.o... 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 for shl_load... no
    checking for shl_load in -ldld... no
    checking for dlopen... no
    checking for dlopen in -ldl... yes
    checking whether a program can dlopen itself... yes
    checking whether a statically linked program can dlopen itself... yes
    checking if libtool supports shared libraries... yes
    checking whether to build shared libraries... yes
    checking whether to build static libraries... no
    configure: creating libtool
    appending configuration tag "CXX" to libtool
    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
    checking if g++ PIC flag -fPIC works... yes
    checking if g++ supports -c -o file.o... yes
    checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
    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 for shl_load... (cached) no
    checking for shl_load in -ldld... (cached) no
    checking for dlopen... (cached) no
    checking for dlopen in -ldl... (cached) yes
    checking whether a program can dlopen itself... (cached) yes
    checking whether a statically linked program can dlopen itself... (cached) yes
    appending configuration tag "F77" to libtool
    checking if libtool supports shared libraries... yes
    checking whether to build shared libraries... yes
    checking whether to build static libraries... no
    checking for f95 option to produce PIC... -fPIC
    checking if f95 PIC flag -fPIC works... yes
    checking if f95 supports -c -o file.o... yes
    checking whether the f95 linker (/usr/bin/ld) supports shared libraries... yes
    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 for msgfmt... /usr/bin/msgfmt
    checking for gmsgfmt... /usr/bin/msgfmt
    checking for xgettext... /usr/bin/xgettext
    checking if C++ programs can be compiled... yes
    checking for strlcat... no
    checking if strlcat needs custom prototype... yes - in libkdefakes
    checking for strlcpy... no
    checking if strlcpy needs custom prototype... yes - in libkdefakes
    checking for main in -lutil... yes
    checking for main in -lcompat... no
    checking for crypt in -lcrypt... yes
    checking for socklen_t... yes
    checking for dnet_ntoa in -ldnet... no
    checking for dnet_ntoa in -ldnet_stub... no
    checking for inet_ntoa... yes
    checking for connect... yes
    checking for remove... yes
    checking for shmat... yes
    checking for sys/types.h... (cached) yes
    checking for stdint.h... (cached) yes
    checking sys/bitypes.h usability... yes
    checking sys/bitypes.h presence... yes
    checking for sys/bitypes.h... yes
    checking for poll in -lpoll... no
    checking Carbon/Carbon.h usability... no
    checking Carbon/Carbon.h presence... no
    checking for Carbon/Carbon.h... no
    checking CoreAudio/CoreAudio.h usability... no
    checking CoreAudio/CoreAudio.h presence... no
    checking for CoreAudio/CoreAudio.h... no
    checking if res_init needs -lresolv... yes
    checking for res_init... yes
    checking if res_init needs custom prototype... no
    checking for killpg in -lucb... no
    checking for int... yes
    checking size of int... 4
    checking for short... yes
    checking size of short... 2
    checking for long... yes
    checking size of long... 4
    checking for char *... yes
    checking size of char *... 4
    checking for dlopen in -ldl... (cached) yes
    checking for shl_unload in -ldld... no
    checking for size_t... yes
    checking size of size_t... 4
    checking for unsigned long... yes
    checking size of unsigned long... 4
    checking sizeof size_t == sizeof unsigned long... yes
    checking crt_externs.h usability... no
    checking crt_externs.h presence... no
    checking for crt_externs.h... no
    checking for _NSGetEnviron... no
    checking for vsnprintf... yes
    checking for snprintf... yes
    checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
    checking for IceConnectionNumber in -lICE... yes
    checking for libXext... yes
    checking for pthread_create in -lpthread... yes
    checking for extra includes... no
    checking for extra libs... no
    checking for libz... -lz
    checking for libpng... -lpng -lz -lm
    checking for libjpeg6b... no
    checking for libjpeg... -ljpeg
    checking for perl... /usr/bin/perl
    checking for Qt... libraries /usr/lib/qt-3.3/lib, headers /usr/lib/qt-3.3/include using -mt
    checking for moc... /usr/lib/qt-3.3/bin/moc
    checking for uic... /usr/lib/qt-3.3/bin/uic
    checking whether uic supports -L ... yes
    checking whether uic supports -nounload ... yes
    checking if Qt needs -ljpeg... no
    checking for rpath... yes
    checking for KDE... configure: error:
    in the prefix, you've chosen, are no KDE headers installed. This will fail.
    So, check this please and use another prefix!
    I am using KDE. Where do I go from here?

    Also, in that output, there are a lot of "no" responses. E.g. "checking for crt_externs.h... no". Do all of these things need to be addressed?

  3. #13
    Linux User
    Join Date
    Aug 2005
    Location
    Peterborough, UK
    Posts
    379
    First off, check if you have kdelibs-dev and/or kdebase-dev (or similar, in both cases) installed. If not, install and try again. If they're already installed, then it is a similar problem to previously.

    Find a file called 'kapplication.h'. Where this file is is where you need to tell the compiler that your KDE headers are installed. I believe you do this by adding '--prefix=<location of kapplication.h>
    \"I am, after all,\" said Pooh, \"a bear of very little brain.\"
    MY PC: Athlon XP64 3000+ on a Asus K8V-X mobo w/1GB of non-descript RAM. AGP - GeForce 2 MX400. PCI - Creative Live! 5.1 soundcard. 140 GB and 120 GB SATA WD drives.

  4. #14
    Just Joined!
    Join Date
    Jan 2005
    Posts
    66
    Firstly, I think the installation worked.

    I have a couple of questions:

    1) for my understanding, what part of the error msg led you to believe that kdelibs-dev and kdebase-dev needed to be installed? It did not specifically name them.

    2) how do I start the application, now that it is installed?

    3) how would I uninstall it (not that I have any intention of doing so, after all that). I am guessing that none of the rpm commands work on applications that have been built and installed from source.

  5. #15
    Linux User St. Joe's Avatar
    Join Date
    Jun 2005
    Location
    USA
    Posts
    271
    Quote Originally Posted by whittler
    1) for my understanding, what part of the error msg led you to believe that kdelibs-dev and kdebase-dev needed to be installed? It did not specifically name them.
    As previously mentioned, when it asks for headers that means you need to install the applicable development libraries.

    Quote Originally Posted by whittler
    2) how do I start the application, now that it is installed?
    Run Command > superkaramba

    Quote Originally Posted by whittler
    3) how would I uninstall it (not that I have any intention of doing so, after all that). I am guessing that none of the rpm commands work on applications that have been built and installed from source.
    You have to save the source install folder, then cd back into that location from a terminal and run a 'make uninstall' session. Be warned, not all source packages have that capability.

    You'd be much better off learning how to make RPM packages.
    It may be that your sole purpose in life is simply to serve as a warning to others.

  6. #16
    Just Joined!
    Join Date
    Jan 2005
    Posts
    66
    Entering superkaramba (or Superkaramba) as a command does not work. I ran "find superkaramba" and it just said file/directory not found.

    Any other ideas? Perhaps the installation failed. I saved the history of the installation output and have uploaded it here if that is helpful. It's all double-dutch to me.

Page 2 of 2 FirstFirst 1 2

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •