I believe it is quite likely that you will not need to build perl yourself at all. 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'm also building perl from source to deal with compiling some of my own modules that have C code. END ------------------------------------------------------------------------------ Philip M. http://culturahq.com/cannot-lock/cannot-lock-autom4te-cache-requests-with-mode.html
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 See sub lock in Autom4te/XFile.pm. The configure script seems to get generated fine. in ../lib/Autom4te/XFile.pm. https://lists.gnu.org/archive/html/autoconf/2007-03/msg00026.html
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 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 appreciate the feedback and look to use reports such as this to guide our efforts at improving our products. I see these warnings on an HP-UX 11 machine.
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 ♦ ♦ | I'm building perl from source because autoconf says it wants perl 5.00503 and I've got 5.00502. autom4te:cannotlockautom4te.cache/requestswithmode2(perhapsyouarerunningmake-jonalameNFSclient?):Functionnotimplemented aclocal-1.9:autom4tefailedwithexitstatus:1 make:***[aclocal.m4]Error1 The total information is like this: checkingforaBSD-compatibleinstall.../usr/bin/install-c checkingwhetherbuildenvironmentissane...yes checkingforgawk...gawk checkingwhethermakesets$(MAKE)...yes checkingbuildsystemtype...x86_64-unknown-linux-gnu checkingforgcc...gcc checkingforCcompilerdefaultoutputfilename...a.out checkingwhethertheCcompilerworks...yes checkingwhetherwearecrosscompiling...no checkingforsuffixofexecutables... 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.
You signed in with another tab or window. Is there anybody who has the same experience or any advise for me? error message? 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
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'm building perl from source because autoconf says it wants perl 5.00503 and I've got 5.00502. ls -ld /usr/bin/perl By default that will be a symlink to /opt/perl/bin/perl on new'ish HP-UX systems. I've run this many times on cygwin, linux and solaris with no trouble.
What are the ownership/perms of the autom4te.cache dir and the /requests file in there? 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 ? Looks like your perl does not properly implement flock. 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?
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 this content Failure mode is a perl exception: ... + autoconf Use of inherited AUTOLOAD for non-method Autom4te::XFile::msg() is deprecated at /usr/share/autoconf/Autom4te/XFile.pm line 238. Do you need more details about this machine? It > works for me.
use Autom4te::Channels qw(msg); ... I'm using m4 1.4.8, autoconf 2.61 and automake 1.10 with the patch so .deps gets created properly. Complete documentation for Perl, including FAQ lists, should be found on this system using `man perl' or `perldoc perl'. weblink This is now fixed in the # CVS version of autoconf.
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 I'm using m4 1.4.8, autoconf 2.61 and automake 1.10 with the patch so .deps gets created properly. Does my configure string help you to remember which were your configure options, by chance?
If not, are there any suggestions either for how to built perl differently or some other way to deal with this? 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 Comment 2 Charlie Brady 2009-04-03 16:26:10 EDT To fix autocont, add: use Autom4te::Channels qw(msg); to XFile.pm. 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 was talking to Florian and he has trouble with getting good performance with TXYZ parallelization because T is so small for him. 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 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. check over here I see you anyway in Paris, right?
David Byron Re: autoreconf warning message: autom4te: cannot lock ... Makes sense. Bartek European Twisted Mass Collaboration member ggscorzato commented Apr 26, 2012 Hi Bartek. See below for just one >>example.
Thank you for taking the time to enter a bug report with us. Not that I reboot that often :) Thanks! -L Do not forward fcntl(2) locks over the wire. David Byron Re: autoreconf warning message: autom4te: cannot lock ... David Byron Re: autoreconf warning message: autom4te: cann...
Bob _______________________________________________ Autoconf mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/autoconf « Return to Gnu - Autoconf - General | 1 view|%1 views Loading... I'm getting a warning message running autoreconf > that I've never seen before. It > works for me. 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
Sign up for free to join this conversation on GitHub. 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 I've run this many times on cygwin, linux and solaris with no trouble. I wrote before seeing your answer ...
I built m4, autoconf and automake on linux and solaris from source using gcc 3.4.x. I built m4, autoconf, and automake from source using gcc 3.2. And providing a fix. RHEL-5.10 (the next RHEL-5 minor release) is going to be the first production phase 2  release of RHEL-5.