[Monotone-devel] ./configure is highly confused

[Rob Weir]

Hi,

I'm trying to build Monotone 0.11 on a reasonably up-to-date Debian Sid
system, and I get some rather odd output from ./configure:

Script started on Fri Apr 30 12:26:19 2004
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 we are using the GNU C++ compiler... no
checking whether g++ accepts -g... no
checking dependency style of g++... none
checking for gcc... gcc
checking whether we are using the GNU C compiler... no
checking whether gcc accepts -g... no
checking for gcc option to accept ANSI C... none needed
checking dependency style of gcc... none
checking for ranlib... ranlib
checking whether gcc and cc understand -c and -o together... yes
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for non-GNU ld... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking whether NLS is requested... yes
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc
checking for iconv... no, consider installing GNU libiconv
checking how to run the C++ preprocessor... g++ -E
checking for ANSI C header files... no
checking unistd.h usability... no
checking unistd.h presence... yes
configure: WARNING: unistd.h: present but cannot be compiled
configure: WARNING: unistd.h: check for missing prerequisite headers?
configure: WARNING: unistd.h: proceeding with the preprocessor's result
configure: WARNING:     ## ------------------------------------ ##
configure: WARNING:     ## Report this to address@hidden ##
configure: WARNING:     ## ------------------------------------ ##
checking for unistd.h... yes
checking errno.h usability... no
checking errno.h presence... yes
configure: WARNING: errno.h: present but cannot be compiled
configure: WARNING: errno.h: check for missing prerequisite headers?
configure: WARNING: errno.h: proceeding with the preprocessor's result
configure: WARNING:     ## ------------------------------------ ##
configure: WARNING:     ## Report this to address@hidden ##
configure: WARNING:     ## ------------------------------------ ##
checking for errno.h... yes
checking for stdint types... (putting them into idna/idn-int.h)... 
checking for stdint uintptr_t... (..)
checking for uintptr_t... no
checking for uintptr_t... no
checking for uintptr_t... no
checking for uintptr_t... no
checking for stdint uintptr_t... 
checking for stdint uint32_t... (..)
checking for uint32_t... no
checking for uint32_t... no
checking for uint32_t... no
checking for uint32_t... no
checking for stdint uint32_t... 
checking for stdint u_int32_t... (..)
checking for u_int32_t... no
checking for u_int32_t... no
checking for u_int32_t... no
checking for stdint u_int32_t... 
checking for stdint datatype model... (..)
checking size of char... configure: error: cannot determine a size for char

Script done on Fri Apr 30 12:26:41 2004

From reading the config.log (attached), it seems that the configure
script is somehow not picking up the correct extension for object files,
so when it tests for their existence, it fails.

I obviously *am* using the GNU C++ compiler, so that is also rather odd.

Re-running a{clocal-1.8,uto{conf,make-1.8}} does nothing but change the
errno.h and unistd.h error messages to tell me to complain to Graydon
instead of GNU :-)

-- 
Rob Weir <address@hidden> | address@hidden  |  Do I look like I want a CC?
Words of the day:      New World Order Kennedy Rumsfield ANC BLU-114/B csystems

config.log
Description: Text document

signature.asc
Description: Digital signature