> "Skip" == Skip Montanaro <[EMAIL PROTECTED]> writes:
Skip> Maybe I can just check a simple shell script into CVS that
Skip> touches the problematic files in the correct order.
There are 3 commonly-used solutions to this problem:
1. Check in generated files and use AM_MAINTAINER_MODE
2. D
>> Third, after executing configure, cvs up reports several
>> unknown files:
>>
>> ? config.log
>> ? Makefile
>> ? config.status
>> ? config.h
>> ? libtool
>> ? stamp-h1
>> ? python/Makefile
>> ? src/Makefile
>> ? src/.deps
>> ? test/Makefile
Skip> I have a few questions. First, what's causing the "cannot remove"
Skip> error when the configure script is executed?
adl> That could be an NFS server which reuse inode numbers. The Linux
adl> user-mode NFS server (unfsd) is known for this. Switch to using
adl> kernel
>>> "Skip" == Skip Montanaro <[EMAIL PROTECTED]> writes:
[...]
Skip> configure: creating ./config.status
Skip> rm: cannot remove `conf5861': Input/output error
[...]
Skip> I have a few questions. First, what's causing the "cannot remove" error
Skip> when the configure script is executed?
Hi Skip,
> Third, after executing configure, cvs up reports several
> unknown files:
>
> ? config.log
> ? Makefile
> ? config.status
> ? config.h
> ? libtool
> ? stamp-h1
> ? python/Makefile
> ? src/Makefile
> ? src/.deps
> ? test/Makefile
> ? test/.
If I check out my project on another machine I am not able to simply execute
./configure && make. On my development machine I verified that I have
generated all files properly:
% cvs up
cvs server: Updating .
cvs server: Updating doc
cvs server: Updating python
cvs server: U
