Re: ./configure cant run qt test program

Roy Souther <[email protected]> Tue, 23 Mar 2004 14:35:55 -0500
Newsgroups gmane.comp.multimedia.avifile.general
Organization Silicon Tao Technology Systems Inc.
Message-ID <1080070555.2668.16.camel@utopiaplanetia>
Same problem here with avifile 0.7.38. I seems that gcc 3.3.2 has an
exit function and the configure test program tries to implement it's own
version. I just hacked the configure program and removed the lines that
redefined the exit operations. 

Lines 10232 to 10235 that read
#ifdef __cplusplus
extern "C" void exit(int);
#endif

AviFile now compiles just fine.

On Sun, 2004-03-21 at 14:08, Hans Wurst wrote:

> Hi,
> I have just tried in vain to install avifile-0.7-0.7.38
> See below for the result of ./configure.
> I am on a PC running redhat 9.
> LD_LIBRARY_PATH=/usr/lib/qt-3.1/lib
> gcc version: 3.2.2 (Red Hat Linux 3.2.2-5)
> Do you have a clou what might go wrong? Shall I stick with an elder version?
> I am using qt for development and have no problems with it (so far).
> Regards and thanks a lot
> Harald
> ---------
> ================================
> [harald@localhost avifile-0.7-0.7.38]$ ./configure
> creating cache ./config.cache
> avifile configure options:
> 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 whether make sets ${MAKE}... yes
> checking for working aclocal-1.4... found
> checking for working autoconf... found
> checking for working automake-1.4... found
> checking for working autoheader... found
> checking for working makeinfo... found
> checking for c++... c++
> checking whether the C++ compiler (c++  ) works... yes
> checking whether the C++ compiler (c++  ) is a cross-compiler... no
> checking whether we are using GNU C++... yes
> checking whether c++ accepts -g... yes
> checking for gcc... gcc
> checking whether the C compiler (gcc  ) works... yes
> checking whether the C compiler (gcc  ) 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... gcc -E
> 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 ranlib... ranlib
> checking for mawk... no
> checking for gawk... gawk
> checking C compiler version... gcc gcc version 3.2.2 20030222 (Red Hat Linux
> 3.2.2-5)
> checking if you need GNU extensions... yes
> checking if gcc supports -finline-limit-200 flag(s)... yes
> checking for Cygwin environment... no
> checking for mingw32 environment... no
> checking build system type... i686-pc-linux-gnu
> 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 for a sed that does not truncate output... /bin/sed
> checking how to recognise dependent libraries... pass_all
> checking for object suffix... o
> checking for executable suffix... no
> checking command to parse /usr/bin/nm -B output... ok
> checking for dlfcn.h... yes
> checking for ranlib... (cached) 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... no
> checking whether -lc should be explicitly linked in... no
> creating libtool
> checking whether byte ordering is bigendian... no
> checking for dlopen in -ldl... yes
> checking for nanosleep in -lposix4... no
> checking for socket in -lsocket... no
> checking for gethostbyname in -lnsl... yes
> checking for kstat_open in -lkstat... no
> checking for lseek64 in -lc... yes
> checking for pthreads... yes
> checking for ANSI C header files... yes
> checking for linux/ioctl.h... yes
> checking for fcntl.h... yes
> checking for limits.h... yes
> checking for malloc.h... yes
> checking for unistd.h... yes
> checking for stdint.h... yes
> checking for assert.h... yes
> checking for sys/types.h... yes
> checking for sys/ioctl.h... yes
> checking for sys/ioccom.h... no
> checking for sys/time.h... yes
> checking for sys/mman.h... yes
> checking for valid sysinfo struct... yes
> checking for working const... yes
> checking for inline... inline
> checking for off_t... yes
> checking for pid_t... yes
> checking for size_t... yes
> checking whether time.h and sys/time.h may both be included... yes
> checking whether struct tm is in sys/time.h or time.h... time.h
> checking for working alloca.h... yes
> checking for alloca... yes
> checking whether gcc needs -traditional... no
> checking whether sys/types.h defines makedev... yes
> checking for 8-bit clean memcmp... yes
> checking for unistd.h... (cached) yes
> checking for getpagesize... yes
> checking for working mmap... yes
> checking whether setvbuf arguments are reversed... no
> checking return type of signal handlers... void
> checking for vprintf... yes
> checking for ftime... yes
> checking for gettimeofday... yes
> checking for strdup... yes
> checking for strstr... yes
> checking for setenv... yes
> checking for unsetenv... yes
> checking for memalign... yes
> checking for scandir... yes
> checking for opendir... yes
> checking for nanosleep... yes
> checking for localtime_r... yes
> checking for asctime_r... yes
> checking for strptime... yes
> checking for vsscanf... yes
> checking for extra asctime_r argument... no
> checking for freetype-config... /usr/bin/freetype-config
> checking for FreeType - version >= 2.0... yes
> checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
> 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 IceConnectionNumber in -lICE... yes
> checking for XGetExtensionVersion in -lXi... yes
> checking for XF86DGAQueryExtension in -lXxf86dga... yes
> checking for XF86VidModeSwitchMode in -lXxf86vm... yes
> checking for pkg-config... /usr/bin/pkg-config
> checking for xft... yes
> checking XFT_CFLAGS... -I/usr/X11R6/include -I/usr/include/freetype2
> checking XFT_LIBS... -L/usr/X11R6/lib -lXft -lfreetype -lXrender
> -lfontconfig
> checking for X11/Xft/Xft.h... yes
> checking for XftDrawStringUtf8 in -lXft... yes
> checking for X11/extensions/Xv.h... yes
> checking for XvCreateImage in -lXv... yes
> checking for X11/extensions/Xinerama.h... yes
> checking for XineramaQueryExtension in -lXinerama... yes
> checking for X11/extensions/dpms.h... yes
> checking whether system has DPMS fce in X11/extensions/dpms.h... yes
> checking for DPMSQueryExtension in -lXdpms... no
> checking for main in -lqt-mt... no
> checking for Qt library (version >= 200)... no
> configure: warning:
> *** Could not run Qt test program, checking why...
> *** Configure discovered/uses these settings:
> *** Qt libraries: /usr/lib/qt-3.1/lib
> *** Qt headers: /usr/lib/qt-3.1/include
> *** Note:
> ***    Compilation of Qt utilities also might be turned off (if not wanted).
> ***    If you are experiencing problems which will not be described
> ***    bellow please report then on '[email protected]' mailing list
> ***    (i.e. some misdetection or omitted path)
> 
> configure: error:
> *** Qt test program compiled, but did not run. This usually means
> *** that the run-time linker is not finding Qt library or finding the wrong
> *** version of Qt. If it is not finding Qt, you will need to set your
> *** LD_LIBRARY_PATH environment variable, or edit /etc/ld.so.conf to point
> *** to the installed location  Also, make sure you have run ldconfig if that
> *** is required on your system.
> ***
> *** If you have an old version installed, it is best to remove it, although
> *** you may also be able to get things to work by modifying LD_LIBRARY_PATH
> ***
> *** i.e. bash> export LD_LIBRARY_PATH=/usr/lib/qt-3.1/lib:$LD_LIBRARY_PATH



Roy Souther
Open Support Guild
Bringing Open concepts to IT support
www.OsGuild.com
signature.asc (application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBAYJGbCbnxcmEBt40RAozEAKDLCz0B7JRyfRgxuV+BFGLQqLkARQCg0UyH
eqq1WgE04K+p2Je2kiR5J2Y=
=x1Mr
-----END PGP SIGNATURE-----