Home > Cannot Lock > Cannot Lock Autom4te Cache

Cannot Lock Autom4te Cache

I don't know how much of this still applies. 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 Golllucci > wrote: > >>Hi all, >> >>I've got a FreeBSD 6.x -current file server running NFS and I mount >>lots of things via NFS on other Freebsd Bartek European Twisted Mass Collaboration member ggscorzato commented Apr 26, 2012 Hi Bartek. have a peek at this web-site

If using XYZT brings substantial performance gains I think it would be wise to keep the code for that maintained for our tmfT friends. error message? 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 Andreas. -- Andreas Schwab, SuSE Labs, address@hidden SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And https://lists.gnu.org/archive/html/autoconf/2007-03/msg00026.html

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'm not sure whether Carsten also had trouble buildig it or whether he was just relating my status from a conversation we had while he was implementing the clover routines. I've run this many times on cygwin, linux and solaris with no trouble. Good news on the fact that it still works, I must have done something wrong then.

Moreover, Carsten has made some changes to the exchange routines, mostly through the addition of "edge" terms to the momentum exchange which were not transferred to the index independent parts. Somewhat but not entirely related: I was wondering whether anyone ever used the XYZT parallelization to do finite-temperature work. I'm getting a warning message running autoreconf > that I've never seen before. 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.

I'm using m4 1.4.8, autoconf 2.61 and automake 1.10 with the patch so .deps gets created properly. I'm also building perl from source to deal with compiling some of my own modules that have C code. Bob _______________________________________________ Autoconf mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/autoconf « Return to Gnu - Autoconf - General | 1 view|%1 views Loading... https://lists.gnu.org/archive/html/autoconf/2007-03/msg00034.html 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'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 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. Can't locate auto/Autom4te/XFile/msg.al in @INC (@INC contains: /usr/share/autoconf /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .) at /usr/share/autoconf/Autom4te/XFile.pm I believe it is quite likely that you will not need to build perl yourself at all.

thanks, Luigi European Twisted Mass Collaboration member kostrzewa commented Apr 26, 2012 No, unfortunately I don't remember. See below for just one >>example. And that is # good enough so override this check. 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 ♦ ♦ |

The configure script seems to get generated fine. Check This Out Is that right? You would need the same build environment for the modules as for the original perl. H _______________________________________________ Autoconf mailing list Autoconf@gnu.org http://lists.gnu.org/mailman/listinfo/autoconf Previous message View by thread View by date Next message autoreconf warning message: autom4te: cannot lock autom4te....

Not that I reboot that often :) Thanks! -L Do not forward fcntl(2) locks over the wire. I built m4, autoconf and automake on linux and solaris from source using gcc 3.4.x. Does my configure string help you to remember which were your configure options, by chance? http://dekovsoft.com/cannot-lock/cannot-lock-autom4te-cache-requests-with.html Bob Proulx RE: autoreconf warning message: autom4te: ...

Reload to refresh your session. [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home] [ptp-dev] compile error From: "lihailong.back" Date: Fri, 8 May 2009 15:47:36 +0800 Delivered-to: ptp-dev@eclipse.org Dkim-signature: v=1; I was talking to Florian and he has trouble with getting good performance with TXYZ parallelization because T is so small for him. I tried > the PerlGcc module but didn't have any luck.

It > works for me.

European Twisted Mass Collaboration member ggscorzato commented Apr 26, 2012 ...sorry ... What are the ownership/perms of the autom4te.cache dir and the /requests file in there? the synthax --with-mpidimension=TXYZ is not allowed. Since phase 2 we'll be addressing only security and critical issues.

Andreas. -- Andreas Schwab, SuSE Labs, [hidden email] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 Makes sense. I'm using m4 1.4.8, autoconf 2.61 and automake 1.10 with the patch so .deps gets created properly. have a peek here I'm quite sure I tried a TXYZ build though so maybe that's the problem.

We recommend upgrading to the latest Safari, Google Chrome, or Firefox. European Twisted Mass Collaboration member kostrzewa commented Apr 26, 2012 Yes, I'll be in Paris too. in ../lib/Autom4te/XFile.pm. Do you need more details about this machine?

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 What is the value of /usr/bin/perl on your > system? > > ls -ld /usr/bin/perl <1:262> % ls -ld /usr/bin/perl ls: /usr/bin/perl: No such file or directory > By default 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 I'm also building perl from source to deal with compiling some of my own modules that have C code.

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 Comment 2 Charlie Brady 2009-04-03 16:26:10 EDT To fix autocont, add: use Autom4te::Channels qw(msg); to XFile.pm. Golllucci pgollucci at p6m7g8.com Sat Mar 19 09:41:54 PST 2005 Previous message: NFS and file locking Next message: just finished install Messages sorted by: [ date ] [ thread ] [ The configure script seems to get generated fine.

Looks like your perl does not properly implement flock. And providing a fix. It > works for me. I notice that upstream now has: ...

Good luck! 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 I'm getting a warning message running autoreconf that I've never seen before. See sub lock in Autom4te/XFile.pm.

Sign up for free to join this conversation on GitHub.