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

Cannot Lock Autom4te Cache Requests With Mode 2

We appreciate the feedback and look to use reports such as this to guide our efforts at improving our products. 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 that I'm getting a warning message running autoreconf that I've never seen before. 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 have a peek at this web-site

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 ♦ ♦ 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 Looks like your perl does not properly implement flock. I built m4, autoconf, and automake from source using gcc 3.2. https://lists.gnu.org/archive/html/autoconf/2007-03/msg00026.html

Thank you for taking the time to enter a bug report with us. Also, if anyone knows how to add this in fstab that would be nice too... checkingforsuffixofobjectfiles...o checkingwhetherweareusingtheGNUCcompiler...yes checkingwhethergccaccepts-g...yes checkingforgccoptiontoacceptANSIC...noneneeded checkingforstyleofincludeusedbymake...GNU checkingdependencystyleofgcc...gcc3 checkingwhethergccandccunderstand-cand-otogether...yes checkingforaBSD-compatibleinstall.../usr/bin/install-c checkingwhethermakesets$(MAKE)...(cached)yes checkingforranlib...ranlib configure:creating./config.status config.status:creatingMakefile config.status:creatingconfig.h config.status:executingdepfilescommands cd.&&/bin/sh/home/adair/compile/org.eclipse.ptp.utils_1.1.0/missing--runaclocal-1.9 /usr/share/aclocal/libgcrypt.m4:23:warning:underquoteddefinitionofAM_PATH_LIBGCRYPT runinfo'(automake)Extendingaclocal' orseehttp://sources.redhat.com/automake/automake.html#Extending-aclocal /usr/share/aclocal/ao.m4:9:warning:underquoteddefinitionofXIPH_PATH_AO autom4te:cannotlockautom4te.cache/requestswithmode2(perhapsyouarerunningmake-jonalameNFSclient?):Functionnotimplemented aclocal-1.9:autom4tefailedwithexitstatus:1 make:***[aclocal.m4]Error1 Thanks so much.Regards 2009-05-08 lihailong.back Follow-Ups:

The configure script seems to get generated fine. This is now fixed in the # CVS version of autoconf. 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. Having said that, I've so far never run into this problem on a number of network file systems.

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

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 It would be especially important, if it does indeed fail to build, to compare to 5.1.6 and perhaps look at the diffs in the relevant files. thanks, Luigi European Twisted Mass Collaboration member kostrzewa commented Apr 26, 2012 No, unfortunately I don't remember. I built perl from source using as many defaults as I could when configuring.

I'm also building perl from source to deal with compiling some of my own modules that have C code. I don't know how much of this still applies. the synthax --with-mpidimension=TXYZ is not allowed. 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

I'm getting a warning message > > running autoreconf that I've never seen before. Check This Out If not, are there any suggestions either for how to built perl differently or some other way to deal with this? configure options? And providing a fix.

You would need the same build environment for the modules as for the original perl. Unfortunately because I'm still porting things to HP-UX it doesn't get all the way through... Reload to refresh your session. http://dekovsoft.com/cannot-lock/cannot-lock-autom4te-cache-requests-with.html European Twisted Mass Collaboration member ggscorzato commented Apr 26, 2012 ...sorry ...

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 More details about my configure.ac? Good news on the fact that it still works, I must have done something wrong then.

Sorry for all the questions.

I've run this many times on cygwin, linux and solaris with no trouble. Here's > > the full output: > > > > $ autoreconf -fvi > > autoreconf: Entering directory `.' > > autoreconf: configure.ac: not using Gettext > > autoreconf: running: aclocal See sub lock in Autom4te/XFile.pm. Then, I find it difficult to imagine which option causes the clash.

Sign in to comment Contact GitHub API Training Shop Blog About © 2016 GitHub, Inc. Skip to site navigation (Press enter) Re: autoreconf warning message: autom4te: cannot lock autom4te.cache/requests with mode 2: Invalid argument Harlan Stenn Sun, 11 Mar 2007 20:50:22 -0800 David, Just a guess 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 have a peek here I'm in the porting group. -DB _______________________________________________ Autoconf mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/autoconf Andreas Schwab Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as

See sub lock in Autom4te/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 We found a workaround. 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.

Andreas Schwab RE: autoreconf warning message: autom4te: cannot l... 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. 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. It works for me.

All locks will be local and not seen by the server and likewise not seen by other NFS clients. I was in the same position of only having 5.00502 available for various reasons and ran into the same problem. autoconf [Top][All Lists] Advanced [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] autoreconf warning message: autom4te: cannot lock autom4te.cache/request From: David Byron Subject: autoreconf warning message: autom4te: cannot lock autom4te.cache/requests with mode There is a small autoconf-lustre compatibility issue.

I'm new to HP-UX and building > perl with my own two hands. Complete documentation for Perl, including FAQ lists, should be found on this system using `man perl' or `perldoc perl'. I didn't build the cygwin tools myself. Complete documentation for Perl, including FAQ lists, should be found on this system using `man perl' or `perldoc perl'.

I'm using m4 1.4.8, autoconf 2.61 and automake 1.10 with the patch so .deps gets created properly. 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 This removes the need to run the rpcbind(8) service and the rpc.statd(8) and rpc.lockd(8) servers on the client. 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

It seems like I can safely ignore this warning. Sign up for free to join this conversation on GitHub. Does my configure string help you to remember which were your configure options, by chance?