Error while running Configure after creating a new project in Kdevelop -3.1.4

[sabari.girish at wipro.com]

Hi,

I have installed the KDE-Cygwin(3.1.4 release) environment along with
Kdevelop 3.0.0b1 release . In Kdevelop,I created a new project
(the simple Hello world). While trying to "Run Configure" from the
"BUILD" menu,
I am getting the following messages below:
________________________________________________________________________
________________________________
*cd /home/sabarig/CPrograms/travelplanner/hello && WANT_AUTOCONF_2_5="1"
WANT_AUTOMAKE_1_6="1" make -f Makefile.cvs && cd
/home/sabarig/CPrograms/travelplanner/hello/debug && CFLAGS="-O0 -g3"
/home/sabarig/CPrograms/travelplanner/hello/configure
--enable-debug=full && cd
/home/sabarig/CPrograms/travelplanner/hello/debug &&
WANT_AUTOCONF_2_5="1" WANT_AUTOMAKE_1_6="1" make -k distclean
*checking for suffix of executables... aclocal
*autoheader
*autoheader: WARNING: Using auxiliary files such as `acconfig.h',
`config.h.bot'
*autoheader: WARNING: and `config.h.top', to define templates for
`config.h.in'
*autoheader: WARNING: is deprecated and discouraged.
*autoheader: 
*autoheader: WARNING: Using the third argument of `AC_DEFINE' and
*autoheader: WARNING: `AC_DEFINE_UNQUOTED' allows to define a template
without
*autoheader: WARNING: `acconfig.h':
*autoheader: 
*autoheader: WARNING: AC_DEFINE([NEED_FUNC_MAIN], 1,
*autoheader: [Define if a function `main' is needed.])
*autoheader: 
*autoheader: WARNING: More sophisticated templates can also be produced,
see the
*autoheader: WARNING: documentation.
*automake
*autoconf
*checking for a BSD-compatible install... /usr/bin/install -c
*checking whether build environment is sane... yes
*checking for gawk... gawk
*checking whether make sets $(MAKE)... yes
*checking for gcc... gcc
*checking for C compiler default output file name... a.exe
*checking whether the C compiler works... yes
*checking whether we are cross compiling... no
*checking for suffix of executables... .exe
*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 for style of include used by make... GNU
*checking dependency style of gcc... gcc3
*checking build system type... i686-pc-cygwin
*checking host system type... i686-pc-cygwin
*checking for a sed that does not truncate output... /usr/bin/sed
*checking for egrep... grep -E
*checking for ld used by gcc... /usr/i686-pc-cygwin/bin/ld.exe
*checking if the linker (/usr/i686-pc-cygwin/bin/ld.exe) is GNU ld...
yes
*checking for /usr/i686-pc-cygwin/bin/ld.exe 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... file_magic ^x86
archive import|^x86 DLL
*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 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 how to run the C++ preprocessor... g++ -E
*checking for g77... g77
*checking whether we are using the GNU Fortran 77 compiler... yes
*checking whether g77 accepts -g... yes
*checking the maximum length of command line arguments... 8192
*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... 
*checking if gcc supports -c -o file.o... yes
*checking whether the gcc linker (/usr/i686-pc-cygwin/bin/ld.exe)
supports shared libraries... yes
*checking whether -lc should be explicitly linked in... yes
*checking how to hardcode library paths into programs... immediate
*checking whether stripping libraries is possible... yes
*checking dynamic linker characteristics... Win32 ld.exe
*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/i686-pc-cygwin/bin/ld.exe
*checking if the linker (/usr/i686-pc-cygwin/bin/ld.exe) is GNU ld...
yes
*checking whether the g++ linker (/usr/i686-pc-cygwin/bin/ld.exe)
supports shared libraries... yes
*checking for g++ option to produce PIC... 
*checking if g++ supports -c -o file.o... yes
*checking whether the g++ linker (/usr/i686-pc-cygwin/bin/ld.exe)
supports shared libraries... yes
*checking how to hardcode library paths into programs... immediate
*checking whether stripping libraries is possible... yes
*checking dynamic linker characteristics... Win32 ld.exe
*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... yes
*checking for g77 option to produce PIC... 
*checking if g77 supports -c -o file.o... yes
*checking whether the g77 linker (/usr/i686-pc-cygwin/bin/ld.exe)
supports shared libraries... yes
*checking how to hardcode library paths into programs... immediate
*checking whether stripping libraries is possible... yes
*checking dynamic linker characteristics... Win32 ld.exe
**** Exited with status: 1 ***
________________________________________________________________________
________________________________

Can anyone help me out of this problem?

Thanks in advance.

Best Regards,
Sabari




Confidentiality Notice

The information contained in this electronic message and any attachments to this message are intended
for the exclusive use of the addressee(s) and may contain confidential or privileged information. If
you are not the intended recipient, please notify the sender at Wipro or Mailadmin at wipro.com immediately
and destroy all copies of this message and any attachments.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-cygwin/attachments/20040202/893dd4c8/attachment.html