Home > Cannot Lock > Cannot Lock Autom4te Cache Requests With

Cannot Lock Autom4te Cache Requests With

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 Unfortunately because I'm still porting things to HP-UX it doesn't get all the way through... This setup appears to > work correctly but now fails in a way that it didn't before. > > One of our builds that uses autoconf started failing with the error: 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 have a peek at this web-site

I'm new to HP-UX and building > perl with my own two hands. 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've run this many times on cygwin, linux and solaris with no trouble. Bob Proulx Reply via email to Search the site The Mail Archive home autoconf - all messages autoconf - about the list Expand Previous message Next message The Mail Archive home https://lists.gnu.org/archive/html/autoconf/2007-03/msg00026.html

Somewhat but not entirely related: I was wondering whether anyone ever used the XYZT parallelization to do finite-temperature work. Sorry for all the questions. David Byron Re: autoreconf warning message: autom... Harlan Stenn RE: autoreconf warning message: autom4te: cannot l...

Then, I find it difficult to imagine which option causes the clash. Having said that, I've so far never run into this problem on a number of network file systems. What are the ownership/perms of the autom4te.cache dir and the /requests file in there? I'm also building perl from source to deal with compiling some of my own modules that have C code.

What are the ownership/perms of the autom4te.cache dir and the /requests file in there? I didn't build the cygwin tools myself. Unfortunately because I'm still porting things to HP-UX it doesn't get all the way through... https://lists.gnu.org/archive/html/autoconf/2007-03/msg00034.html Kent Engström Reply via email to Search the site The Mail Archive home lustre-discuss - all messages lustre-discuss - about the list Expand Previous message Next message The Mail Archive home

We appreciate the feedback and look to use reports such as this to guide our efforts at improving our products. Comment 11 Pavel Raiskup 2013-03-07 09:15:26 EST Hello Charlie, (In reply to comment #10) > (In reply to comment #9) > > > I am sorry, but it is now too Terms Privacy Security Status Help You can't perform that action at this time. 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

You need to mount the clients with "-o flock" to get globally-coherent flock (at some performance impact) or "-o localflock" to get local-node-only flock (at minimal performance impact). http://gnu-autoconf.7623.n7.nabble.com/autoreconf-warning-message-autom4te-cannot-lock-autom4te-cache-requests-with-mode-2-Invalid-argument-td9124.html European Twisted Mass Collaboration member ggscorzato commented Apr 26, 2012 I also tried without tsplitpar and with/without halfspinor and they all build. I'm also building perl from source to deal with compiling some of my own modules that have C code. 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 ?

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. Check This Out Ashley Nicholls Re: [Lustre-discuss] Autoconf/Automake problem when r... I didn't build the cygwin tools myself. I notice that upstream now has: ...

I tried > the PerlGcc module but didn't have any luck. Does my configure string help you to remember which were your configure options, by chance? If I make that change, the build does not die with an exception, but instead terminates with: ... /bin/sh ./libtool --tag=CC --mode=link gcc -DUSE_MMAP -DWITH_RSYNC_PAD -O3 -fomit-frame-pointer -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes Source 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

You are right. 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. 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:

Since phase 2 we'll be addressing only security and critical issues.

I built m4, autoconf, and automake from source using gcc 3.2. Bob _______________________________________________ Autoconf mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/autoconf « Return to Gnu - Autoconf - General | 1 view|%1 views Loading... David Byron Re: autoreconf warning message: autom4te: cann... You signed out in another tab or window.

I was in the same position of only having 5.00502 available for various reasons and ran into the same problem. This is from an rpm spec file %prep build section for an HP-UX build of autoconf. HesabımAramaHaritalarYouTubePlayHaberlerGmailDriveTakvimGoogle+ÇeviriFotoğraflarDaha fazlasıDokümanlarBloggerKişilerHangoutsGoogle'a ait daha da fazla uygulamaOturum açınGizli alanlarGrupları veya mesajları ara Gnu - Autoconf › Gnu - Autoconf - General Search everywhere only in this topic Advanced Search autoreconf warning have a peek here And that is # good enough so override this check.

You would need the same build environment for the modules as for the original perl. I built m4, autoconf and automake on linux and solaris from source using gcc 3.4.x. 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? I don't know how much of this still applies.

I'm getting a warning message running autoreconf that I've never seen before. And providing a fix. That being said, this bug tracking system is not a mechanism for requesting support, and we are not able to guarantee the timeliness or suitability of a resolution. Home | New | Search | [?] | Reports | Requests | Help | NewAccount | Log In [x] | Forgot Password Login: [x] | Report Bugzilla Bug Legal Skip to

If this issue is critical or in any way time sensitive, please raise a ticket through your regular Red Hat support channels to make certain it receives the proper attention and 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 There is a small autoconf-lustre compatibility issue. RHEL-5.10 (the next RHEL-5 minor release) is going to be the first production phase 2 [1] release of RHEL-5.

What is the value of /usr/bin/perl on your system? If using XYZT brings substantial performance gains I think it would be wise to keep the code for that maintained for our tmfT friends. David Byron Re: autoreconf warning message: autom4te: cannot lock ... European Twisted Mass Collaboration member kostrzewa commented Apr 24, 2012 Unfortunately I can't remember how exaclty I tried to build the index independent version but it failed to build (although it

Yes.