Home > Cannot Lock > Cannot Lock Autom4te Cache Requests With

Cannot Lock Autom4te Cache Requests With

I'm getting a warning message running autoreconf > that I've never seen before. Reload to refresh your session. You signed in with another tab or window. Terms Privacy Security Status Help You can't perform that action at this time. his comment is here

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 Comment 2 Charlie Brady 2009-04-03 16:26:10 EDT To fix autocont, add: use Autom4te::Channels qw(msg); to XFile.pm. And providing a fix. Add the mode # so that this runs on the older perl. https://lists.gnu.org/archive/html/autoconf/2007-03/msg00026.html

See sub lock in Autom4te/XFile.pm. 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 When I run it, the expected things happen.

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.... Good luck! 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 Comment 3 Charlie Brady 2009-04-03 16:29:09 EDT Here's the relevant upstream mailing list discussion: http://www.mail-archive.com/autoconf-patches@gnu.org/msg01152.html Comment 9 Pavel Raiskup 2013-03-07 07:17:09 EST I am sorry, but it is now too late

I'm new to HP-UX and building > perl with my own two hands. Andreas Dilger Re: [Lustre-discuss] Autoconf/Automake problem wh... I believe it is quite likely that you will not need to build perl yourself at all. 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

Is that right? So, at least my typical usage of indexindepgeom is not broken. Format For Printing -XML -Clone This Bug -Top of page First Last Prev Next This bug is not in your last search results. I've run this many times on cygwin, linux and solaris with no trouble.

If using XYZT brings substantial performance gains I think it would be wise to keep the code for that maintained for our tmfT friends. I built m4, autoconf, and automake from source using gcc 3.2. Since phase 2 we'll be addressing only security and critical issues. 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.

It > works for me. this content 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. Somewhat but not entirely related: I was wondering whether anyone ever used the XYZT parallelization to do finite-temperature work. The configure script seems to get generated fine.

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 Also, if anyone knows how to add this in fstab that would be nice too... You signed out in another tab or window. http://culturahq.com/cannot-lock/cannot-lock-autom4te-cache-requests-with-mode.html I built m4, autoconf and automake on linux and solaris from source using gcc 3.4.x.

Sign up for free to join this conversation on GitHub. There is a small autoconf-lustre compatibility issue. I tried > the PerlGcc module but didn't have any luck.

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:

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 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 Do you need more details about this machine? It > works for me.

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 I'm using m4 1.4.8, autoconf 2.61 and automake 1.10 with the patch so .deps gets created properly. It works for me. check over here 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

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. 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. This was for the 2.59 version now quite dated. # We only have perl 5.005_02 available at the moment. 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.

What are the ownership/perms of the autom4te.cache dir and the /requests file in there? ls -ld /usr/bin/perl By default that will be a symlink to /opt/perl/bin/perl on new'ish HP-UX systems. I'm getting a warning message > > running autoreconf that I've never seen before.


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