On 2008-08-07 12:51:31 +0200, Vincent Lefevre wrote: > I could reproduce this problem with two different servers (for the > first one, the server directory is over NFS, but for the second one, > it is just the local disk of the machine). I retried with the second > server by using "-o cache=no" and the problem disappeared.
In fact, "-o cache=no". The problem is not always reproducible, whether it is used or not. It seems that this depends on the old contents of the file. If I start from an empty configure file, then the file always remains empty (and at the same date) after running autoconf. If there's no configure file when running autoconf, a correct file is created. When the file had been truncated to 860160 bytes, the old file had 861098 bytes. Also, the problem occurs when using "-o workaround=all" too. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
