|
2009-12-18, 22:20
|
#375 |
"Serge"
Mar 2008
Phi(4,2^7658614+1)/2
24·593 Posts |
I remember that for CVS, there were some magic lines that could be added right into the C source, but I don't know these for SVN. So, the easiest is to do it manually, before the compilation.
|
|
|
|
2009-12-18, 22:55
|
#376 |
|
Tribal Bullet
Oct 2004
3·1,181 Posts |
With CVS you could put '$Id' anywhere in the file and CVS would fill it in with the version number of that file, the date and the submitter.
SVN can do the same, but first you have to tell SVN that the 'put in the Id' property is required for the file. However, in both cases the revision number is for that file alone, not for the whole repository, which is what a printed out version number should really refer to. |
|
|
|
|
2009-12-18, 23:41
|
#377 |
Jun 2003
The Texas Hill Country
44116 Posts |
If you have a tree checked out with subversion, there is a command `svnversion` which will give you the version number.
The following code is in a project that I am using at the moment. It uses python to generate a standard C header file as a part of the build process. You could do something similar in other languages and/or to write other files that contain the version number as a derived source Code:
richard:trunk rkw$ cat Sources/Misc/svnversion.py
import os
v = os.popen("svnversion").read()
cmd = """echo '@"%s"' """ % (v,)
os.system(cmd)
if v.find(":") <> -1: v = v.split(":")[1]
v = v[:-1]
if v[-1] == 'M': v = v[:-1]
cmd = """echo '#define SVN_VERSION @"%s"' > svnversion.h""" % (v,)
os.system(cmd)
richard:trunk rkw$
|
|
|
|
|
2010-01-02, 18:56
|
#378 |
Nov 2008
2×33×43 Posts |
I'm getting a reproducible crash of 11e (with a Windows error message "has encountered a problem") on a c89:
Code:
-> Q0=455001, QSTEP=5000. -> makeJobFile(): q0=455000, q1=460000. -> makeJobFile(): Adjusted to q0=455001, q1=460000. -> Lattice sieving algebraic q-values from q=455001 to 460000. => "C:/Documents and Settings/Jan/My Documents/gnfs/gnfs-lasieve4I11e.exe" -k -o spairs.out -v -n0 -a test.job -> Return value 65280. Updating job file and terminating... =>"C:/Documents and Settings/Jan/My Documents/gnfs/cat.exe" spairs.out >> spairs.add -> makeJobFile(): q0=455000, q1=460000. -> makeJobFile(): Adjusted to q0=455001, q1=460000. Terminating... Code:
n: 76340020872443700405976546699600978634844613332488572752137860827922968109996041396366149 m: Y0: -2670937544050135455792 Y1: 190522541639 c0: -38029740146529207265105243 c1: 67163981508843850300 c2: -161368812018872 c3: 294605015 c4: 1500 skew: 557427.87 rlim: 600000 alim: 455000 lpbr: 25 lpba: 25 mfbr: 43 mfba: 43 rlambda: 2.2 alambda: 2.2 q0: 455001 qintsize: 4999 #q1:460000 Last fiddled with by 10metreh on 2010-01-02 at 18:58 |
|
|
|
|
2010-01-13, 10:47
|
#379 |
Jun 2003
Ottawa, Canada
3×17×23 Posts |
In case you missed it in the msieve forum, there is a new factmsieve.py (python script) for running ggnfs and msieve. It fixes some bugs in the perl script and has some new features. You can check out the details here:
http://www.mersenneforum.org/showthread.php?t=12981 Jeff. |
|
|
|
|
2010-01-17, 19:41
|
#380 |
"Ed Hall"
Dec 2009
Adirondack Mtns
382310 Posts |
Would someone possibly know why my linux compiled ggnfs doesn't include the ...11e file?
I worked around it with factMsieve.pl by commenting the ...11e portions and redirecting to the ...12e file - not ideal, but it at least runs. However, I don't know enough about python to modify that file and I'd rather run ...11e for the proper sized numbers. Linux - Fedora 11, 1.8G AMD, 1.5G Ram ggnfs-0.77.1.tar.gz |
|
|
|
|
2010-01-17, 19:53
|
#381 | |
|
Nov 2008
2·33·43 Posts |
Quote:
Code:
svn co https://ggnfs.svn.sourceforge.net/svnroot/ggnfs ggnfs |
|
|
|
|
|
2010-01-17, 20:18
|
#382 | |
|
"Ed Hall"
Dec 2009
Adirondack Mtns
3,823 Posts |
Quote:
I get a gazzillion warnings, etc., but no errors and it completes gracefully. But, there is no ...11e with this version either.  There is an ...11e folder in the ../build.vc/vc9 folder, but that is the only reference I can find. Actually, this appears to be the same version as the tar.gz file I have. |
|
|
|
|
|
2010-01-17, 20:50
|
#383 |
"Serge"
Mar 2008
Phi(4,2^7658614+1)/2
24×593 Posts |
The special sievers for 64-bit linux are in
http://ggnfs.svn.sourceforge.net/vie...l/lasieve4_64/ (if you did svn already, then you will find it under src/experimental/lasieve4_64/ ) If you have 32-bit linux, then you need src/lasieve4/ Edit Makefile and add lasieveI11e if it's not mentioned there. |
|
|
|
|
2010-01-17, 22:05
|
#384 | |
|
"Ed Hall"
Dec 2009
Adirondack Mtns
1110111011112 Posts |
Quote:
Editing the Makefile to add ...11e seems to have done the trick. I now have ...11e in my bin folder. Now, I can go back to experimenting with the new python file... Thanks much! |
|
|
|
|
|
2010-01-19, 19:56
|
#385 |
Jun 2007
Moscow,Russia
2058 Posts |
nice c108 split
Almoust perfect c108 of (392-1)*2^392+1 split:
Code:
r1=103534965904516731071641017437208071126168526287342677 r2=2471474986733510011259721016575181383606687556902973937 |
|
|
|
 |
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Installation of GGNFS | LegionMammal978 | Msieve | 17 | 2017-01-20 19:49 |
| Running other programs while running Prime95. | Neimanator | PrimeNet | 14 | 2013-08-10 20:15 |
| Error running GGNFS+msieve+factmsieve.py | D. B. Staple | Factoring | 6 | 2011-06-12 22:23 |
| GGNFS or something better? | Zeta-Flux | Factoring | 1 | 2007-08-07 22:40 |
| ggnfs | ATH | Factoring | 3 | 2006-08-12 22:50 |
