Open xanthe-cat opened 6 months ago
I’ve uploaded the $F_{14}$ proof and my “quick” shell script and output, after discovering that the script causes a chain of seg faults. I definitely think a script to create needed symlinks, make cofact, and do some quick testing has usefulness.
Scripts and other files included along with previous versions of cofact
Gary’s 0.6 to 0.8 versions distributed as
.zip
files included:Cathy’s versions included:
-cpr
and-upr
commands utilising VDF proofs. I now have generated VDF proofs for Fermat numbers as small as $F{14}$, so we could include a $F_{14}$ proof for minimum size and runtime when self-testing.pellucid
program (and a shell script with output) for testing Pell–Lucas numbers (not directly relevant to this repository);cofact
compiled to use only GMP, without gwnum (principally owing to difficulties cross-compiling cofact to run on both Intel-based Macs and Apple Silicon, seeing as gwnum relies on x86-family and similar processors).These are “add-ons” to the repository which were useful for packaging
cofact
up as.zip
files for distribution, so their presence here is debatable. We could decide to include useful shell scripts and output for whatever reason is convincing.Build scripting
One other difficulty with
cofact.c
and theMakefile
is that thegwnum
files have to be available locally as they are referenced with#include "gwnum.h"
(rather than<gwnum.h>
; so in the.zip
files that were used for distribution, Gary included a collection of pre-set symbolic links so thatgwnum.a
,gwnum.h
, … would be easily found by unzipping within thegwnum
directory.Also, the 0.75c version in the
cxc
branch uses proof validation code from George Woltman that requires an additional 3 symlinks to files in the Prime95/mprime source distribution in order to compile, so it seems it would be highly useful to have a bash script to create the required sym links and then runmake
. If we’re going to do that, then we could do other things that are easily scriptable, such as runningcofact
on a suite of very quick tests to determine that it has built correctly.Documentation
I’ll restore the
README.md
file once we’re happy with the two branches and all of the added files. Should we have two documentation pages for the two branches?