Cannot Lock Autom4te Cache Requests With Mode

Add the mode # so that this runs on the older perl. autom4te:cannotlockautom4te.cache/requestswithmode2(perhapsyouarerunningmake-jonalameNFSclient?):Functionnotimplemented aclocal-1.9:autom4tefailedwithexitstatus:1 make:***[aclocal.m4]Error1 The total information is like this: checkingforaBSD-compatibleinstall.../usr/bin/install-c checkingwhetherbuildenvironmentissane...yes checkingforgawk...gawk checkingwhethermakesets$(MAKE)...yes checkingbuildsystemtype...x86_64-unknown-linux-gnu checkingforgcc...gcc checkingforCcompilerdefaultoutputfilename...a.out checkingwhethertheCcompilerworks...yes checkingwhetherwearecrosscompiling...no checkingforsuffixofexecutables... Is there anybody who has the same experience or any advise for me? Thanks much for any information you have on this. -DB _______________________________________________ Autoconf mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/autoconf Harlan Stenn Reply | Threaded Open this post in threaded view ♦ ♦ | have a peek at this web-site

If you have access to the Internet, point your browser at http://www.perl.com/, the Perl Home Page. > Depending upon your release of HP-UX the vendor perl there > should be quite Failure mode is a perl exception: ... + autoconf Use of inherited AUTOLOAD for non-method Autom4te::XFile::msg() is deprecated at /usr/share/autoconf/Autom4te/XFile.pm line 238. For information on how to contact the Red Hat production support team, please visit: https://www.redhat.com/support/process/production/#howto Thanks, Pavel Note You need to log in before you can comment on or make changes Already have an account? why not try these out

I didn't build the cygwin tools myself. Check This Out Bob Proulx RE: autoreconf warning message: autom4te: ... What are the ownership/perms of the autom4te.cache dir and the /requests file in there? Note that this option will only be honored when performing the initial mount, it will be silently ignored if used while updating the mount options.

On 11.11 that would be v5.6.1 and on 11.23 that would be v5.8.0. > > I believe it is quite likely that you will not need to > > build perl

Sign up for free to join this conversation on GitHub. This removes the need to run the rpcbind(8) service and the rpc.statd(8) and rpc.lockd(8) servers on the client. I tried the PerlGcc module but didn't have any luck. -DB reply via email to [Prev in Thread] Current Thread [Next in Thread] autoreconf warning message: autom4te: cannot lock autom4te.cache/requests with I checked that with: ./configure --enable-sse3 --enable-mpi --with-mpidimension=XYZ --disable-halfspinor --enable-indexindepgeom --enable-tsplitpar --with-limedir=${limedir} --with-lemondir=${lemondir} --with-lapack=${lapacklib} CC="${mpicomp} -O3" CFLAGS="-msse3 -O3" the configuration and the build work.

The routines need to be extended in any case though because of the changes introduced as a result of the clover term. What are the ownership/perms of the autom4te.cache > dir and the /requests file in there? <1:264> % ls -ld autom4te.cache/ autom4te.cache/requests drwxr-x--- 2 ecloud porting 4096 Mar All locks will be local and not seen by the server and likewise not seen by other NFS clients. have a peek here You would need the same build environment for the modules as for the original perl.

I provide the (simple) fix for you in *2009*!! If you are unfamiliar with git, I can help you with some commands that will make it easy to find the differences I mentioned above. Bug494042 - autoconf fails if build sandbox is NFS mounted without proper locking support Summary: autoconf fails if build sandbox is NFS mounted without proper locking support Status: CLOSED NEXTRELEASE Aliases: I originally set things up this way to handle problems on solaris where the compiler used to build perl was no longer available so compiling some modules failed.

Do it here instead of as a patch # so we can preserve timestamps because otherwise we need to bootstrap # the tools. This is from an rpm spec file %prep build section for an HP-UX build of autoconf. What is the value of /usr/bin/perl on your system? Bob _______________________________________________ Autoconf mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/autoconf « Return to Gnu - Autoconf - General | 1 view|%1 views Loading...

I'm getting a warning message running autoreconf that I've never seen before. I did a quick google search and it seems like autoconf requires globally coherent locks and these are often not enabled because they induce a minor performance hit. But the configure should complain. It works for me.

It > works for me. See below for just one >>example. What are the ownership/perms of the autom4te.cache dir and the /requests file in there? This was for the 2.59 version now quite dated. # We only have perl 5.005_02 available at the moment.

I have successfully used 5.00502 for a long time. It would be very helpful, I think (if the code will remain maintained in the future) if you tried building and testing it with the various parallelizations since you know this See sub lock in Autom4te/XFile.pm. It > works for me.