configuring cygwin-setup: ../cfgaux/configure: No such file or directory

Max Bowsher maxb@ukf.net
Mon Oct 6 21:47:00 GMT 2003


Perry Pupp wrote:
> --- Max Bowsher wrote:
>> 
>> Please give more context, starting from "cvs
>> checkout setup". Something
>> rather odd is happening.
>> 
> 
> (Good idea. Here is my procedure from scratch,
> with a couple versions thrown in, and entire
> configure output.)
> 
> (PS: Yep, I did run the bootstrap; actually
> I didn't have a configure script until I did
> that.)
> 
> 
> 
> $ cd ..
> 
> $ mkdir t2
> 
> $ cd t2
> 
> $ cvs -z3 -d
>> pserver:anoncvs@sources.redhat.com:/cvs/cygwin-apps co setup
> 
> cvs server: Updating setup
> U setup/.cvsignore
> ...
> 
> $ cd setup
> 
> $ sh bootstrap.sh
> Running bootstrap.sh in libgetopt++
> ./bootstrap.sh: not found

Well, that obviously isn't right.
Is there no libgetopt++/bootstrap.sh in your checkout?

> Continuing with bootstrap in current directory
> configure.in: installing `cfgaux/install-sh'
> configure.in: installing `cfgaux/mkinstalldirs'
> configure.in: installing `cfgaux/missing'
> Makefile.am: installing `cfgaux/compile'
> Makefile.am: installing `cfgaux/depcomp'
> Autotool bootstrapping complete.
> 
...
> $ mkdir bld
> 
> $ cd bld
> 
> $ ../configure
> 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 whether to enable maintainer-specific
> portions of Makefiles... no
> checking Whether to build inilint... no
> checking Whether to enable rsync support... no
> checking for g++... g++
> checking for C++ compiler default output... 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 g++ accepts -g... yes
> checking for style of include used by make... GNU
> checking dependency style of g++... gcc3
> 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 whether gcc and cc understand -c and -o
> together... yes
> checking for flex... flex
> checking for yywrap in -lfl... yes
> checking lex output file root... lex.yy
> checking whether yytext is a pointer... no
> checking for bison... bison -y
> 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/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...
> 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 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...
> yes
> checking for gcc option to produce PIC...
> checking if gcc supports -c -o file.o... yes
> checking whether the gcc linker (/usr/bin/ld) 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/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...
> checking if g++ supports -c -o file.o... yes
> checking whether the g++ 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... 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/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... Win32
> ld.exe
> checking for windres... windres
> checking for main in -lmingw32... yes
> checking alloca.h usability... yes
> checking alloca.h presence... yes
> checking for alloca.h... yes
> checking errno.h usability... yes
> checking errno.h presence... yes
> checking for errno.h... yes
> checking string usability... no

This isn't right either.

Look in config.log for more info on this error.

> checking string presence... yes
> configure: WARNING: string: present but cannot be
> compiled
> configure: WARNING: string: check for missing
> prerequisite headers?
> configure: WARNING: string: proceeding with the
> preprocessor's result

Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/



More information about the Cygwin mailing list