Skip Montanaro <[EMAIL PROTECTED]> writes:
|> % cvs up
|> cvs server: Updating .
|> cvs server: Updating python
|> cvs server: Updating src
|> cvs server: Updating test
|> % ./configure
|> checking for a BSD compatible install... /usr/bin/install -c
|> checking whether build environment is sane... yes
|> checking for mawk... mawk
|> checking whether make sets ${MAKE}... yes
|> checking for g++... g++
|> checking for C++ compiler default output... a.out
|> ... bunch of normal msgs elided ...
|> checking if gcc static flag -static works... yes
|> checking if gcc supports -c -o file.o... ./configure: cd: conftest: Not a
|directory
|> rm: cannot remove `conftest': Input/output error
|> rmdir: conftest: No such file or directory
|> yes
|> checking if gcc supports -c -o file.lo...
|> checking if gcc supports -fno-rtti -fno-exceptions... no
|> checking whether the linker (/usr/bin/ld) supports shared libraries... yes
|> ... bunch more normal msgs elided ...
|> checking for rmdir... yes
|> checking for strdup... yes
|> configure: creating ./config.status
|> config.status: creating Makefile
|> config.status: error: cannot find input file: Makefile.in
|> montanaro@tttmgl:~/src/alf$
|>
|> When I look at config.log in the region of the error output I see
|>
|> configure:5495: checking if gcc supports -c -o file.lo
I think you should rather look at the point where "checking if gcc
supports -c -o file.o" is done.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 N�rnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
