[Bug 63781] New: ./configure fails when building project from SDL template

[meldroc at frii.com]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=63781     
           Summary: ./configure fails when building project from SDL
                    template
           Product: kdevelop
           Version: unspecified
          Platform: Debian testing
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-devel at kdevelop.org
        ReportedBy: meldroc at frii.com


Version:           Kdevelop 3.0.0a5 (Gideon), from Debian packages at http://people.debian.org/~njordan/unstable/ (using KDE KDE 3.1.3)
Installed from:    Debian testing/unstable Packages
Compiler:          gcc 3.3.2 automake version 1.7.6, autoconf version 2.1.3
OS:          Linux

I started by creating a new project using Project->New, and used the Simple SDL Program template under the C++ category.  Then, using the default main.cpp file, and changing nothing, I ran automake & friends, which I presume invokes aclocal, automake, autoconf, etc.  Doing that gives me the following output:

* cd /home/meldroc/projects/bugtest1 && WANT_AUTOCONF_2_5="1" WANT_AUTOMAKE_1_6="1" make -f Makefile.cvs 
* aclocal 
* autoheader 
* WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot' 
* WARNING: and `config.h.top', to define templates for `config.h.in' 
* WARNING: is deprecated and discouraged. 
*  
* WARNING: Using the third argument of `AC_DEFINE' and 
* WARNING: `AC_DEFINE_UNQUOTED' allows to define a template without 
* WARNING: `acconfig.h': 
*  
* WARNING: AC_DEFINE([NEED_MAIN], 1, 
* WARNING: [Define if a function `main' is needed.]) 
*  
* WARNING: More sophisticated templates can also be produced, see the 
* WARNING: documentation. 
* configure.in:18: warning: AC_ARG_PROGRAM was called before AC_CANONICAL_TARGET 
* automake 
* autoconf 
* *** Success ***

Then I ran ./configure (or Build -> Run Configure) and got the following output & error:

* cd /home/meldroc/projects/bugtest1 && /home/meldroc/projects/bugtest1/configure 
* installing -c 
* checking whether build environment is sane... yes 
* checking for gawk... gawk 
* checking whether make sets $(MAKE)... yes 
* checking for g++... g++ 
* checking for C++ compiler default output... 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 g++ accepts -g... yes 
* checking for style of include used by make... GNU 
* checking dependency style of g++... gcc3 
* checking build system type... i686-pc-linux-gnu 
* checking host system type... i686-pc-linux-gnu 
* 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 ANSI C... none needed 
* checking dependency style of gcc... gcc3 
* 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 how to run the C preprocessor... gcc -E 
* 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 how to run the C++ preprocessor... g++ -E 
* checking for g77... no 
* checking for f77... no 
* checking for xlf... no 
* checking for frt... no 
* checking for pgf77... no 
* checking for fl32... no 
* checking for af77... no 
* checking for fort77... no 
* checking for f90... no 
* checking for xlf90... no 
* checking for pgf90... no 
* checking for epcf90... no 
* checking for f95... no 
* checking for fort... no 
* checking for xlf95... no 
* checking for lf95... no 
* checking for g95... no 
* checking whether we are using the GNU Fortran 77 compiler... no 
* checking whether accepts -g... no 
* 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 
* compiling yes (gcc) 
* 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 
* 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 
* compiling yes (g++) 
* 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 
* appending configuration tag "F77" to libtool 
* -L/usr/lib -lSDL -lpthread 
* -I/usr/include/SDL -D_REENTRANT 
* checking target system type... i686-pc-linux-gnu 
* checking for sdl-config... /usr/bin/sdl-config 
* checking for SDL - version >= 1.2.0... no 
* *** Could not run SDL test program, checking why... 
* *** The test program failed to compile or link. See the file config.log for the 
* *** exact error that occured. This usually means SDL was incorrectly installed 
* *** or that you have moved SDL since it was installed. In the latter case, you 
* *** may want to edit the sdl-config script: /usr/bin/sdl-config 
* configure: error: *** SDL version 1.2.0 not found! 
* *** Exited with status: 1 ***

Obviously, the automake/autoconf scripts to check for the prescense of SDL have failed.

I know I have SDL correctly installed on my system, because I have a correctly working KDevelop 2.1.5 project where I manually hacked the automake/autoconf files to add the SDL check macros.