mersenneforum.org latest SVN 1677
 Register FAQ Search Today's Posts Mark Forums Read

 2012-01-07, 14:56 #1 ATH Einyen     Dec 2003 Denmark 26·72 Posts latest SVN 1677 There is no "build.vc9" folder when I get the latest svn? and the required Makefile.in is not in the build.vc10 folder. "Autoreconf -i" fails: Code: configure.in:623: required file build.vc9/Makefile.in' not found configure.in:623: required file build.vc9/assembler/Makefile.in' not found configure.in:623: required file build.vc9/ecm/Makefile.in' not found configure.in:623: required file build.vc9/libecm/Makefile.in' not found configure.in:623: required file build.vc9/tune/Makefile.in' not found Makefile.am: installing ./depcomp' autoreconf: automake failed with exit status: 1 Last fiddled with by ATH on 2012-01-07 at 14:57
2012-01-07, 15:45   #2
WraithX

Mar 2006

1110110012 Posts

Quote:
 Originally Posted by ATH There is no "build.vc9" folder when I get the latest svn? and the required Makefile.in is not in the build.vc10 folder. "Autoreconf -i" fails:

The files to edit are Makefile.am and configure.in. Remove the references to build.vc9 in both of those files, then 'autoreconf -i' will succeed.

https://gforge.inria.fr/frs/?group_i...elease_id=6762

This way you can bypass the autoreconf step. :) Let me know how it goes and I'll talk with you later.

 2012-01-07, 15:48 #3 ATH Einyen     Dec 2003 Denmark 313610 Posts Thank you. I was considering getting the 6.4 source, but wasn't sure if it was the same as the latest SVN 1677. So I wanted to ask first to get the latest SVN.
 2012-01-07, 16:03 #4 WraithX     Mar 2006 11×43 Posts Yeah, there are only a few minor changes between ecm-6.4 and svn 1677, so there shouldn't be any worry about missing features. Actually, Paul has already updated the svn. It is now at 1678. 'autoreconf -i', 'make', and 'make check' all complete successfully for me. Hopefully they will for you too.
 2012-01-07, 16:35 #5 fivemack (loop (#_fork))     Feb 2006 Cambridge, England 24·3·7·19 Posts I am probably missing something obvious in the documentation, but I can't see how to compile ecm-6.4 against mpir. Compiling it against gmp-4.3.2 gives me an executable which runs more slowly than ecm-6.2 as shipped by ubuntu.
 2012-01-07, 16:45 #6 ATH Einyen     Dec 2003 Denmark 26×72 Posts It was already at SVN 1681 when I got it now :) Maybe you should post which SVN the official "ecm-6.4.tar.gz" release is (and future releases): https://gforge.inria.fr/frs/?group_i...elease_id=6762 Just a suggestion, it would be nice to know. Fivemack: Compile MPIR with: ./configure --enable-gmpcompat make make install make check then compile GMP-ECM same way as with GMP. Last fiddled with by ATH on 2012-01-07 at 16:47
 2012-01-07, 17:41 #7 jasonp Tribal Bullet     Oct 2004 2·29·61 Posts Alex and I are updating the stage 2 code for P+-1 in a separate branch, you won't see any of that in the upcoming release (but the repository version number increments all the same)
2012-01-07, 18:34   #8
WraithX

Mar 2006

1110110012 Posts

Quote:
 Originally Posted by ATH It was already at SVN 1681 when I got it now :) Maybe you should post which SVN the official "ecm-6.4.tar.gz" release is (and future releases): https://gforge.inria.fr/frs/?group_i...elease_id=6762 Just a suggestion, it would be nice to know.
I asked Paul which SVN version each release was based on. He let me know that the information is in the file README.dev.

It currently has the following information:

Version 6.2 is r1290, 6.2.1 is r1307, 6.3 is r1501, 6.4 is r1672.

 Similar Threads Thread Thread Starter Forum Replies Last Post science_man_88 Hardware 19 2018-01-25 01:06 david314 Msieve 1 2013-07-01 16:45 ATH GMP-ECM 10 2012-07-29 17:15 davieddy Lounge 0 2011-01-21 19:29 [CZ]Pegas Software 3 2002-08-23 17:05

All times are UTC. The time now is 20:30.

Tue May 18 20:30:46 UTC 2021 up 40 days, 15:11, 0 users, load averages: 1.58, 1.63, 1.78

This forum has received and complied with 0 (zero) government requests for information.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.
A copy of the license is included in the FAQ.