AW: Tutorial project build problem
Kevin Gray
kgray at iols.net
Thu Aug 26 21:09:51 BST 1999
Micko Roland wrote:
> Taking a look at the configure output I found two things that look strange
> to me
>
> - Checking for X doesn't show the path to X-include and X-library path
> But QT and KDE are working, as here the path are explicitly mentioned
> --> Try to start configure with ./configure --x-i=<Path to your X-Header
> files> --x-l=<Path to your X library files>
>
> - -lucb -lcompat -l.... not found.
> --> Try to start configure with ./configure --x-i=<Path to your X-Header
> files> --x-l=<Path to your X library files> --extra-libs=<Path where these
> libs are installed>
>
> I hope this helps.
>
> Roland Micko
> ICN CA MR EG 2
>
> SIEMENS AG
> Hofmannstr. 51
> 81359 München
>
> Tel.: +4989/722-21632
> Fax.: +4989/722-47420
> email: roland.micko at icn.siemens.de
>
I'm not sure if this was my problem, I have included the runtime response I get
from configure if this would be of any help, it seems to find my X11 libraries
and headers ok and I have checked that this, is indeed where they are. I also
got a post from Gal who thought it may be to do with the ld.so not linking my
libraries so I did a ldconfig -v just incase this hadn't been updated but alas
I still get the same response. I believe my main concern now is the......
configure: In function `int main()':
configure:911: warning: implicit declaration of function `int XtMalloc(...)'
/usr/bin/ld: cannot open -lXt: No such file or directory
collect2: ld returned 1 exit status
configure: failed program was:
#line 908 "configure"
#include "confdefs.h"
I have checked the libXt.so file and it exists under my /usr/X11R6/lib
directory so I don't understand how it tells me there is no such file. As for
the extra libs and extra includes, I have no idea what these should be. Is
there an RPM package for them, if not there is a good chance I haven't
installed them, at the moment I'm mainly sticking to using RPM, till I get
better aquainted with using source. Thanks for all the help, if anything I'm
learning a lot more about the system and where all the files are located.
Thanks
Kevin Gray
loading cache ./config.cache
checking for gcc... gcc
checking whether the C compiler (gcc -static ) works... yes
checking whether the C compiler (gcc -static ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking how to run the C++ preprocessor... g++ -E
checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for ranlib... ranlib
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking for main in -lcompat... no
checking for main in -lcrypt... yes
checking for the third argument of getsockname... socklen_t
checking for dnet_ntoa in -ldnet... no
checking for dnet_ntoa in -ldnet_stub... no
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for killpg in -lucb... no
checking for Qt... libraries /usr/lib, headers /usr/include/qt
checking if Qt compiles without flags... yes
checking for moc... /usr/bin/moc
checking for rpath... yes
checking for bool... yes
checking host system type... i586-pc-linux-gnu
checking target system type... i586-pc-linux-gnu
checking build system type... i586-pc-linux-gnu
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking for a C-Compiler... gcc
checking whether the C compiler (gcc -g -O2 -static ) works... yes
checking whether the C compiler (gcc -g -O2 -static ) is a cross-compiler...
no
checking whether we are using GNU C... (cached) yes
checking how to run the C preprocessor... gcc -E
checking for a C++-Compiler...
checking for g++... g++
checking whether the C++ compiler (g++ -O0 -g3 -Wall -static ) works...
yes
checking whether the C++ compiler (g++ -O0 -g3 -Wall -static ) is a
cross-compiler... no
checking whether we are using GNU C++... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... -static
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the linker (/usr/bin/ld) supports shared libraries... yes
checking command to parse /usr/bin/nm -B output... yes
checking how to hardcode library paths into programs... immediate
checking for /usr/bin/ld option to reload object files... -r
checking dynamic linker characteristics... Linux ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking for objdir... .libs
creating libtool
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for KDE... libraries /usr/lib, headers /usr/include
checking for extra includes... no
checking for extra libs... no
checking for kde headers installed... yes
checking for kde libraries installed... yes
checking for KDE paths... done
configure: error: configure could not run a little KDE program to test the
environment.
Since it had compiled and linked before, it must be a strange problem on your
system.
Look at config.log for details. If you are not able to fix this, please contact
Stephan Kulow <coolo at kde.org>.
*** failed ***
More information about the KDevelop
mailing list