Home > Cannot Lock > Cannot Lock Autom4te Cache Requests

Cannot Lock Autom4te Cache Requests

Andreas Dilger Re: [Lustre-discuss] Autoconf/Automake problem wh... 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 in ../lib/Autom4te/XFile.pm. I wrote before seeing your answer ... http://dekovsoft.com/cannot-lock/cannot-lock-autom4te-cache-requests-with.html

I've run this many times on cygwin, linux and solaris with no trouble. I see these warnings on an HP-UX 11 machine. I'm building perl from source because autoconf says it wants perl 5.00503 and I've got 5.00502. Here's the full output: > > $ autoreconf -fvi > autoreconf: Entering directory `.' > autoreconf: configure.ac: not using Gettext > autoreconf: running: aclocal --force -I m4 > autom4te: cannot lock

thanks, Luigi European Twisted Mass Collaboration member kostrzewa commented Apr 26, 2012 On 25/04/12 20:11, ggscorzato wrote: autom4te: cannot lock autom4te.cache/requests with mode 2: Function not implemented Hi Luigi, are you Thanks much. Free forum by Nabble Edit this page NFS and file locking Philip M. It > works for me.

I tried autoconf (version 2.63), but I get: autom4te: cannot lock autom4te.cache/requests with mode 2: Function not implemented How should I produce the configure file now? This one issue is fixed in RHEL-6 therefore I am closing the bug as NEXTRELEASE. [1] https://access.redhat.com/support/policy/updates/errata/ Comment 10 Charlie Brady 2013-03-07 08:54:53 EST (In reply to comment #9) > I When I run it, the expected things happen. Thanks much for any information you have on this. -DB reply via email to [Prev in Thread] Current Thread [Next in Thread] autoreconf warning message: autom4te: cannot lock autom4te.cache/requests with mode

Looks like your perl does not properly implement flock. When I run it, the expected things happen. 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. Source All locks will be local and not seen by the server and likewise not seen by other NFS clients.

In fact, I get: configure: error: Only t, xt, xyt, xyzt, x, xy, xyz parallelisation available one should use the synthax: --with-mpidimension=XYZT in this case it builds (in the tests that configure options? Personal Open source Business Explore Sign up Sign in Pricing Blog Support Search GitHub This repository Watch 10 Star 20 Fork 39 etmc/tmLQCD Code Issues 77 Pull requests 8 Projects This is now fixed in the # CVS version of autoconf.

Bob _______________________________________________ Autoconf mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/autoconf « Return to Gnu - Autoconf - General | 1 view|%1 views Loading... http://gnu-autoconf.7623.n7.nabble.com/autoreconf-warning-message-autom4te-cannot-lock-autom4te-cache-requests-with-mode-2-Invalid-argument-td9124.html Here's some info from config.log: uname -m = 9000/782 uname -r = B.11.00 uname -s = HP-UX uname -v = A configure:2929: checking host system type configure:2944: result: hppa2.0w-hp-hpux11.00 > I I built m4, autoconf and automake on linux and solaris from source using gcc 3.4.x. I see you anyway in Paris, right?

Unfortunately because I'm still porting things to HP-UX it doesn't get all the way through... Check This Out I tried the PerlGcc module but didn't have any luck. -DB _______________________________________________ Autoconf mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/autoconf Bob Proulx Reply | Threaded Open this post in threaded view ♦ ♦ It works for me. Yes.

My AccountSearchMapsYouTubePlayNewsGmailDriveCalendarGoogle+TranslatePhotosMoreShoppingWalletFinanceDocsBooksBloggerContactsHangoutsEven more from GoogleSign inHidden fieldsSearch for groups or messages Gnu - Autoconf › Gnu - Autoconf - General Search everywhere only in this topic Advanced Search autoreconf warning message: Sign in to comment Contact GitHub API Training Shop Blog About © 2016 GitHub, Inc. You would need the same build environment for the modules as for the original perl. Source Reload to refresh your session.

European Twisted Mass Collaboration member ggscorzato commented Apr 25, 2012 I tried to compile what I downloaded now from: git clone https://github.com/etmc/tmLQCD.git I see that the configure file is not in All machines involved are CentOS 5 based > and run the 2.6.18-164.11.1.el5_lustre.1.8.2 kernel. So, at least my typical usage of indexindepgeom is not broken.

Good luck!

Already have an account? I built m4, autoconf, and automake from source using gcc 3.2. I built perl from source using as many defaults as I could when configuring. I notice that upstream now has: ...

The routines need to be extended in any case though because of the changes introduced as a result of the clover term. I provide the (simple) fix for you in *2009*!! I'm new to HP-UX and building perl with my own two hands. -DB _______________________________________________ Autoconf mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/autoconf Bob Proulx Reply | Threaded Open this post in threaded view have a peek here I will try it together with the other options and let you know.

More details about my configure.ac? use Autom4te::Channels qw(msg); ... Do you need more details about this machine? I'm getting a warning message running autoreconf that I've never seen before.

H _______________________________________________ Autoconf mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/autoconf David Byron-3 Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ RE: autoreconf Do you need more details about this machine? If using XYZT brings substantial performance gains I think it would be wise to keep the code for that maintained for our tmfT friends. Here's the full output: $ autoreconf -fvi autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --force -I m4 autom4te: cannot lock autom4te.cache/requests with mode 2: Invalid argument

for f in $(find . -type f -print0 \ | xargs -r0 grep -l 5.005_03); do sed 's/5.005_03/5.005_02/' $f > $f.new chmod --reference $f $f.new I tried > the PerlGcc module but didn't have any luck. Comment 2 Charlie Brady 2009-04-03 16:26:10 EDT To fix autocont, add: use Autom4te::Channels qw(msg); to XFile.pm. 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

Here's some info from config.log: uname -m = 9000/782 uname -r = B.11.00 uname -s = HP-UX uname -v = A configure:2929: checking host system type configure:2944: result: hppa2.0w-hp-hpux11.00 > I By adding the > line 'use Autom4te::Channels qw(msg);' and 'use Automake::Channels qw(msg);' > to the respective XFile.pm autoconf becomes more verbose and produces: > "autom4te: cannot lock autom4te.cache/requests with mode 2: error message?