Home > Cannot Lock > Cannot Lock Autom4te Cache Requests

Cannot Lock Autom4te Cache Requests

Bob Proulx RE: autoreconf warning message: autom4te: ... 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 I see you anyway in Paris, right? 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. his comment is here

I'm building perl from source because autoconf says it wants perl 5.00503 and I've got 5.00502. It seems like I can safely ignore this warning. We found a workaround. in ../lib/Autom4te/XFile.pm.

Unfortunately because I'm still porting things to HP-UX it doesn't get all the way through... 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 might try to reproduce it in two weeks time.

And that is # good enough so override this check. 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.... European Twisted Mass Collaboration member ggscorzato commented Apr 18, 2012 version? I get _lots_ of file locking issues.

Andreas. -- Andreas Schwab, SuSE Labs, [email protected] 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 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 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 Already have an account?

It > works for me. 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 The routines need to be extended in any case though because of the changes introduced as a result of the clover term. I'm getting a warning message running autoreconf that I've never seen before.

Do you need more details about this machine? http://gnu-autoconf.7623.n7.nabble.com/autoreconf-warning-message-autom4te-cannot-lock-autom4te-cache-requests-with-mode-2-Invalid-argument-td9124.html 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 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. Is that right?

Andreas Schwab RE: autoreconf warning message: autom4te: cannot l... this content Terms Privacy Security Status Help You can't perform that action at this time. Sorry for all the questions. See sub lock in Autom4te/XFile.pm.

RHEL-5.10 (the next RHEL-5 minor release) is going to be the first production phase 2 [1] release of RHEL-5. 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 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 http://culturahq.com/cannot-lock/cannot-lock-autom4te-cache-requests-with-mode.html I built m4, autoconf, and automake from source using gcc 3.2.

I'm getting a warning message > > running autoreconf that I've never seen before. Also, if anyone knows how to add this in fstab that would be nice too... When I run it, the expected things happen.

I'm getting a warning message running autoreconf > that I've never seen before.

Andreas Dilger Re: [Lustre-discuss] Autoconf/Automake problem wh... The configure script seems to get generated fine. 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 Looks like your perl does not properly implement flock.

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 ♦ ♦ sed 's/\(mkdir.*\)/\1, 0755/' bin/autoreconf.in > # bin/autoreconf.in.new chmod --reference bin/autoreconf.in bin/autoreconf.in.new touch --reference bin/autoreconf.in bin/autoreconf.in.new mv -f bin/autoreconf.in.new bin/autoreconf.in Perhaps that will help. > I'm also building 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. check over here I notice that upstream now has: ...

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 The configure script seems to get generated fine. Good news on the fact that it still works, I must have done something wrong then. If so, that could be the culprit.

You signed in with another tab or window. 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 David Byron Re: autoreconf warning message: autom4te: cannot lock ... I don't know how much of this still applies.

This is now fixed in the # CVS version of autoconf. Do you need more details about this machine? 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 ? 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.

More details about my configure.ac? 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 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 Yes.

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. 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 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


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