Home > Cannot Lock > Cannot Lock Autom4te Cache Requests With Mode

Cannot Lock Autom4te Cache Requests With Mode

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 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 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 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 his comment is here

Format For Printing -XML -Clone This Bug -Top of page First Last Prev Next This bug is not in your last search results. I didn't build the cygwin tools myself. The configure script seems to get generated fine. 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 https://lists.gnu.org/archive/html/autoconf/2007-03/msg00026.html

Bob Proulx RE: autoreconf warning message: autom4te: ... error message? Since phase 2 we'll be addressing only security and critical issues. 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

Comment 1 Charlie Brady 2009-04-03 16:25:13 EDT Line 238 is within sub lock(): 238: msg ($make_j ? 'fatal' : 'unsupported', 239: "cannot lock $file with mode $mode: $!" . ($make_j ? 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 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 ] [ Also, if anyone knows how to add this in fstab that would be nice too...

This was for the 2.59 version now quite dated. # We only have perl 5.005_02 available at the moment. Unfortunately because I'm still porting things to HP-UX it doesn't get all the way through... All locks will be local and not seen by the server and likewise not seen by other NFS clients. https://lists.gnu.org/archive/html/autoconf/2007-03/msg00034.html I'm building perl from source because autoconf says it wants perl 5.00503 and I've got 5.00502.

I'm getting a warning message running autoreconf > that I've never seen before. More details about my configure.ac? Bob _______________________________________________ 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 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.

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 http://gnu-autoconf.7623.n7.nabble.com/autoreconf-warning-message-autom4te-cannot-lock-autom4te-cache-requests-with-mode-2-Invalid-argument-td9124.html You signed in with another tab or window. 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. I haven't tried it yet...., but is it better to use the -L or run these 3 services ?

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 content I'm also building perl from source to deal with compiling some of my own modules that have C code. H _______________________________________________ Autoconf mailing list [email protected] http://lists.gnu.org/mailman/listinfo/autoconf Previous message View by thread View by date Next message autoreconf warning message: autom4te: cannot lock autom4te.... 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. David Byron Re: autoreconf warning message: autom4te: cann... Already have an account? weblink RHEL-5.10 (the next RHEL-5 minor release) is going to be the first production phase 2 [1] release of RHEL-5.

I'm new to HP-UX and building > perl with my own two hands. I built m4, autoconf, and automake from source using gcc 3.2. Comment 2 Charlie Brady 2009-04-03 16:26:10 EDT To fix autocont, add: use Autom4te::Channels qw(msg); to XFile.pm.

I'm wondering, will NFSv4 fix this or switching to samba ? >>If not, I'd be gratefull for suggestions. >> >>Thanks in advance! >> >>vegeta# df >>krillin:/usr/ports 15390126 3159612 10999304 22% /usr/ports

It > works for me. Not that I reboot that often :) Thanks! -L Do not forward fcntl(2) locks over the wire. I've run this many times on cygwin, linux and solaris with no trouble. 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 ♦ ♦ |

It > works for me. Reload to refresh your session. Somewhat but not entirely related: I was wondering whether anyone ever used the XYZT parallelization to do finite-temperature work. check over here Unfortunately because I'm still porting things to HP-UX it doesn't get all the way through...

END ------------------------------------------------------------------------------ Philip M. Gollucci >>Consultant >>E-Mail: pgollucci at p6m7g8.com >>URL : http://p6m7g8.net/Resume/resume.shtml >>Phone : 301.254.5198 >> >>$Id: .signature,v 1.7 2004/09/05 23:46:37 philip Exp $ >> >>_______________________________________________ >>freebsd-questions at freebsd.org mailing list >>http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>To unsubscribe, 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 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.

Try this scriptly patch. 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 I'm getting a warning message running autoreconf that I've never seen before. I'm getting a warning message running autoreconf > that I've never seen before.

Yes. 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 Bob _______________________________________________ Autoconf mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/autoconf « Return to Gnu - Autoconf - General | 1 view|%1 views Loading... I wrote before seeing your answer ...

I'm using m4 1.4.8, autoconf 2.61 and automake 1.10 with the patch so .deps gets created properly. I don't know how much of this still applies. 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. 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.

Good news on the fact that it still works, I must have done something wrong then. I've run this many times on cygwin, linux and solaris with no trouble. 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. It seems like I can safely ignore this warning.


  • © Copyright 2017 culturahq.com. All rights reserved.