On Thu, Apr 27, 2006 at 06:46:54PM +0200, Ralf Wildenhues wrote: > Invocation of autom4te fails currently on FreeBSD with NFS-mounted > directories: > | ../build-alpha-unknown-freebsd6.0/tests/autoconf > | autom4te: cannot lock autom4te.cache/requests with mode 2 (perhaps you are > running make -j on a lame NFS client?): Operation not supported
These system are configured improperly; they need to run `rpc.lockd'. > Of course, this prevents any successful autoconf runs, and thus causes > massive testsuite failure. It'd be great if somebody more fluent with > perl and locking issues look into this and debug the respective lock > method in lib/Autom4te/XFile.pm. The method looks fine. I guess we can add EOPNOTSUPP to the list of permitted error codes. Alternatives include ignoring all flock errors, or simply letting folks fix their configuration problems. I am inclined to recognize and ignore EOPNOTSUPP. I will prepare a patch later tonight or tomorrow. > Seen on the HP testdrive hosts, with > | This is perl, v5.8.6 built for alpha-freebsd [Side note: this system seems to have a number of rough edges. I had wanted to test on it, but it always dropped my connection as soon as I authenticated. It turns out that my .cshrc makes its /bin/csh dump core!]
