AW: Tutorial project build problem

[Micko Roland]

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

> -----Ursprüngliche Nachricht-----
> Von:	Kevin Gray [SMTP:kgray at iols.net]
> Gesendet am:	Donnerstag, 26. August 1999 06:43
> An:	kdevelop at fara3.cs.uni-potsdam.de
> Betreff:	Tutorial project build problem
> 
> I've been trying to follow the tutorial that came with KDeveloper, but
> everytime
> I go through the wizard setup it stops with the message below and I can't
> seem
> to resolve this problem with the configure script.  It does state that I
> don't
> have the extra includes and extra libs for KDE, and I'm not sure where or
> what I
> need to get or if I need them.  I'm running RedHat 6.0 I have all the
> developer
> packages as far as I know using the available RPMs KDE 1.1.1, QT 1.44
> release
> 6.  I have looked around for people having similar problems and can't seem
> to
> find anything, I was thinking that it was a RedHat problem with the mix up
> with
> where KDE was installed,  which I did fix with making a symlink through
> /opt/kde
> --> /usr I would be gratefull if anyone has come across this problem and
> knows
> what is causing the problem.  I also get a core dump after the configure
> script
> terminates with the message........
> 
> 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 ***
> 
> 
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
> 
> configure:558: checking for gcc
> configure:671: checking whether the C compiler (gcc -O0 -g3 -Wall ) works
> configure:687: gcc -o conftest -O0 -g3 -Wall   conftest.c  1>&5
> configure:684: warning: return-type defaults to `int'
> configure:713: checking whether the C compiler (gcc -O0 -g3 -Wall ) is a
> cross-compiler
> configure:718: checking whether we are using GNU C
> configure:727: gcc -E conftest.c
> configure:746: checking whether gcc accepts -g
> configure:778: checking how to run the C++ preprocessor
> configure:796: g++ -E  conftest.C >/dev/null 2>conftest.out
> configure:822: checking for X
> configure:839: g++ -E  conftest.C >/dev/null 2>conftest.out
> configure:915: g++ -o conftest -O0 -g3 -Wall   conftest.C -lXt  1>&5
> 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"
> 
> int main() {
> XtMalloc()
> ; return 0; }
> configure:1082: checking for a BSD compatible install
> configure:1135: checking whether build environment is sane
> configure:1173: checking whether make sets ${MAKE}
> configure:1202: checking for ranlib
> configure:1242: checking for ld used by GCC
> configure:1299: checking if the linker (/usr/bin/ld) is GNU ld
> GNU ld version 2.9.1 (with BFD 2.9.1.0.23)
> configure:1315: checking for BSD-compatible nm
> configure:1352: checking whether ln -s works
> configure:1381: checking for main in -lcompat
> configure:1396: gcc -o conftest -O0 -g3 -Wall   conftest.c -lcompat   1>&5
> /usr/bin/ld: cannot open -lcompat: No such file or directory
> collect2: ld returned 1 exit status
> configure: failed program was:
> #line 1389 "configure"
> #include "confdefs.h"
> 
> int main() {
> main()
> ; return 0; }
> configure:1417: checking for main in -lcrypt
> configure:1432: gcc -o conftest -O0 -g3 -Wall   conftest.c -lcrypt   1>&5
> configure:1453: checking for the third argument of getsockname
> configure:1478: g++ -c -O0 -g3 -Wall  conftest.C 1>&5
> configure:1535: checking for dnet_ntoa in -ldnet
> configure:1557: g++ -o conftest -O0 -g3 -Wall   conftest.C -ldnet   1>&5
> /usr/bin/ld: cannot open -ldnet: No such file or directory
> collect2: ld returned 1 exit status
> configure: failed program was:
> #line 1543 "configure"
> #include "confdefs.h"
> /* Override any gcc2 internal prototype to avoid an error.  */
> #ifdef __cplusplus
> extern "C"
> #endif
> /* We use char because int might match the return type of a gcc2
>     builtin and then its argument prototype would still apply.  */
> char dnet_ntoa();
> 
> int main() {
> dnet_ntoa()
> ; return 0; }
> configure:1579: checking for dnet_ntoa in -ldnet_stub
> configure:1601: g++ -o conftest -O0 -g3 -Wall   conftest.C -ldnet_stub
> 1>&5
> /usr/bin/ld: cannot open -ldnet_stub: No such file or directory
> collect2: ld returned 1 exit status
> configure: failed program was:
> #line 1587 "configure"
> #include "confdefs.h"
> /* Override any gcc2 internal prototype to avoid an error.  */
> #ifdef __cplusplus
> extern "C"
> #endif
> /* We use char because int might match the return type of a gcc2
>     builtin and then its argument prototype would still apply.  */
> char dnet_ntoa();
> 
> int main() {
> dnet_ntoa()
> ; return 0; }
> configure:1623: checking for gethostbyname
> configure:1654: g++ -o conftest -O0 -g3 -Wall   conftest.C  1>&5
> configure:1719: checking for connect
> configure:1750: g++ -o conftest -O0 -g3 -Wall   conftest.C  1>&5
> configure:1816: checking for remove
> configure:1847: g++ -o conftest -O0 -g3 -Wall   conftest.C  1>&5
> configure:1914: checking for shmat
> configure:1945: g++ -o conftest -O0 -g3 -Wall   conftest.C  1>&5
> configure:2014: checking for killpg in -lucb
> configure:2036: g++ -o conftest -O0 -g3 -Wall   conftest.C -lucb   1>&5
> /usr/bin/ld: cannot open -lucb: No such file or directory
> collect2: ld returned 1 exit status
> configure: failed program was:
> #line 2022 "configure"
> #include "confdefs.h"
> /* Override any gcc2 internal prototype to avoid an error.  */
> #ifdef __cplusplus
> extern "C"
> #endif
> /* We use char because int might match the return type of a gcc2
>     builtin and then its argument prototype would still apply.  */
> char killpg();
> 
> int main() {
> killpg()
> ; return 0; }
> configure:2113: checking for Qt
> tried /usr/lib/qt/lib
> tried /usr/X11R6/lib
> configure:2215: g++ -o conftest -O0 -g3 -Wall -I/usr/include/qt
> -L/usr/lib
> -L/usr/X11R6/lib conftest.C  -lqt -lXext -lX11  1>&5
> configure:2267: checking if Qt compiles without flags
> configure:2306: g++ -o conftest -O0 -g3 -Wall -I/usr/include/qt
> -L/usr/X11R6/lib conftest.C -lqt -lXext -lX11  1>&5
> configure:2358: checking for moc
> configure:2444: checking for rpath
> configure:2473: checking for bool
> configure:2493: g++ -c -O0 -g3 -Wall  conftest.C 1>&5
> configure: In function `int main()':
> configure:2489: warning: unused variable `bool aBool'
> configure:2542: checking host system type
> configure:2563: checking target system type
> configure:2581: checking build system type
> configure:2643: checking for working aclocal
> configure:2656: checking for working autoconf
> configure:2669: checking for working automake
> configure:2682: checking for working autoheader
> configure:2695: checking for working makeinfo
> configure:2747: checking for a C-Compiler
> configure:2859: checking whether the C compiler (gcc -O0 -g3 -Wall ) works
> configure:2875: gcc -o conftest -O0 -g3 -Wall   conftest.c  1>&5
> configure:2872: warning: return-type defaults to `int'
> configure:2901: checking whether the C compiler (gcc -O0 -g3 -Wall ) is a
> cross-compiler
> configure:2906: checking whether we are using GNU C
> configure:2980: checking how to run the C preprocessor
> configure:3001: gcc -E  conftest.c >/dev/null 2>conftest.out
> configure:3042: checking for a C++-Compiler
> configure:3048: checking for g++
> configure:3164: checking whether the C++ compiler (g++ -O0 -g3 -Wall -s)
> works
> configure:3180: g++ -o conftest -O0 -g3 -Wall  -s conftest.C  1>&5
> configure:3206: checking whether the C++ compiler (g++ -O0 -g3 -Wall -s)
> is a
> cross-compiler
> configure:3211: checking whether we are using GNU C++
> configure:3220: g++ -E conftest.C
> configure:3360: checking whether NLS is requested
> configure:3388: checking for msgfmt
> configure:3422: checking for gmsgfmt
> configure:3465: checking for xgettext
> configure:3513: checking for KDE
> configure:3649: checking for extra includes
> configure:3677: checking for extra libs
> configure:3804: checking for kde headers installed
> configure:3851: g++ -c -O0 -g3 -Wall -I/usr/include -I/usr/include/qt
> -I/usr/X11R6/include  conftest.C
> configure:3859: checking for kde libraries installed
> configure:3862: /bin/sh ./libtool --mode=link g++ -o conftest -O0 -g3
> -Wall
> -I/usr/include -I/usr/include/qt  -I/usr/X11R6/include  -s -L/usr/lib
> -L/usr/X11R6/lib conftest.C  -lkdecore -lqt -lXext -lX11  -rpath /usr/lib
> -rpath
> /usr/X11R6/lib  1>&5
> g++ -o conftest -O0 -g3 -Wall -I/usr/include -I/usr/include/qt
> -I/usr/X11R6/include -s -L/usr/lib -L/usr/X11R6/lib conftest.C -lkdecore
> -lqt
> -lXext -lX11 -Wl,--rpath -Wl,/usr/lib -Wl,--rpath -Wl,/usr/X11R6/lib
> configure:3871: checking for KDE paths
> 
> Thanks to anyone who got this far down, I'm sure it could be a shortage of
> some
> libraries but I'm at a loss as to what they are.......  please let me know
> if
> you need any more info I really would like to learn how to code QT and KDE
> and I
> guess I have a lot to learn about the configure script :-)
> 
> Thanks
> 
> Kevin Gray
>