Compiling Phrot

[rogue]

Originally Posted by Anonymous

As for the YEALIB variable, though--you're right, if I run that ls command, I get blank response (essentially a "no such file or directory" on my system). But, isn't yeafft.h supposed to be in the glucas src directory? After all, that is the correct path to my glucas directory. Is my glucas source incomplete, or something weird like that?

From the glucas directory, do "./configure". It will create the yeafft.h file. You might need to modify src/Makefile to set CFLAGS options, which are listed earlier in this thread.

[mdettweiler]

Originally Posted by rogue

From the glucas directory, do "./configure". It will create the yeafft.h file. You might need to modify src/Makefile to set CFLAGS options, which are listed earlier in this thread.

Okay, I did that, and it made the yeafft.h file. Now, when I tried to do a make from within the glprov directory, it apparently could find yeafft.h OK. However, it still couldn't yeafft.a and a few other files:

gcc  -g -Wall \
        -O3 -mtune=nocona -msse2 -msse2 \
        -DMODULAR_REDUCE_1 \
        -I./libs/libs -I../glucas/src \
        -o phrot.c2d \
        glprov.c \
        ../glucas/src/libyeafft.a
gcc: ../glucas/src/libyeafft.a: No such file or directory
glprov.c:93:23: error: mathtypes.h: No such file or directory
glprov.c:95:18: error: x86.h: No such file or directory
In file included from glprov.c:123:
../glucas/src/yeafft.h:47:29: error: yeafft_defines.h: No such file or directory
glprov.c:147:19: error: fpnum.c: No such file or directory
glprov.c:148:21: error: fpextra.c: No such file or directory
glprov.c:247: error: expected specifier-qualifier-list before ‘int64’
glprov.c:302: error: expected specifier-qualifier-list before ‘int64’
glprov.c:318: error: expected declaration specifiers or ‘...’ before ‘int64’
glprov.c: In function ‘describeVar’:
glprov.c:322: error: expected ‘)’ before ‘PRINTF_I64’

There were loads more of errors, all similar in style to the ones found near the end of my snippet above (presumably from functions and whatnot that are in the files that it couldn't find).

Please feel free to respond via email as you had suggested before. You can use the "mail this user" link on my profile, or if you'd rather email me directly, my email address, as mentioned earlier in this thread, is bugmesticky AT googlemail DOT com.

[mdettweiler]

Originally Posted by rogue

Go to this thread for version 0.51. It is Phil's version with some changes I've introduced.

With one caveat, however: you'll have to compile it from source. I'm working on compiling a 32-bit Linux version, and I'll post a binary when I get it to work.

Maybe someone a little more experienced with compiling could try a Windows build? (From what I can tell, compiling for Windows is much more complicated than compiling for Linux.)

[rogue]

Originally Posted by Anonymous

Please feel free to respond via email as you had suggested before. You can use the "mail this user" link on my profile, or if you'd rather email me directly, my email address, as mentioned earlier in this thread, is bugmesticky AT googlemail DOT com.

e-mail sent. Once we get this issue worked out, I will start a new thread for phrot with better instructions.

[mdettweiler]

Originally Posted by rogue

e-mail sent. Once we get this issue worked out, I will start a new thread for phrot with better instructions.

Okay, cool.

[em99010pepe]

Originally Posted by rogue

Go to this thread for version 0.51. It is Phil's version with some changes I've introduced.

I am using version 0.5 and -o flag doesn't work. Where can I find version 0.51? On that thread it is not clear where to download a compiled version.

Let me say something. If you guys want more help to the project you need to have the tools available to help. I don't know how to compile and I don't want to waste my time studying how to do it.

[mdettweiler]

Originally Posted by em99010pepe

I am using version 0.5 and -o flag doesn't work. Where can I find version 0.51? On that thread it is not clear where to download a compiled version.

Let me say something. If you guys want more help to the project you need to have the tools available to help. I don't know how to compile and I don't want to waste my time studying how to do it.

There's no compiled version of 0.51 available yet, except for MacIntel; I'm working privately via email on compiling a Linux x86 version. As for a Windows version--any of you programmers out there want to take a whack at it?

0.51 is relatively new, that's why there's not much in the way of precompiled binaries available yet. Hopefully that will change soon.

In the meantime, LLR/PRP will still work just as well as it always has.

[masser]

Originally Posted by em99010pepe

Let me say something. If you guys want more help to the project you need to have the tools available to help. I don't know how to compile and I don't want to waste my time studying how to do it.

Hi Carlos,

Thanks for offering to help. I really appreciate having your previous and any present contributions to the Riesel/Sierpinski base 5 project.

Right now, as a moderator of the SRB5 project, I view phrot as a great tool if you can build it and use it efficiently. Based on the many recent comments, it certainly seems that rogue has made many positive additions to the code, but its use is not completely automated yet. Because of this, LLRNET is still the preferable testing method; both maintenance of the records/statistics pages and the automation of the testing make LLRNET the desired means of testing from the project's perspective.

Let me reiterate - phrot is a great tool, but it is not completely automated. If you just want to help the project, use the LLRNET queues. If you want to experiment with phrot, that is fine too. I will help in whatever way I can, although rogue is certainly the expert on phrot and perhaps can assist you more readily.

Thanks again, everybody, for the resources you are contributing and the attention you are giving the codes.

[em99010pepe]

masser,

phrot doesn't run on my quad-core, must be the settings of its compilation...I don't know. I tested on an AMD and it works fine. So I think I'll unreserve the work you sent me. Sorry.
6 cores added to LLRnet.

Carlos

[kar_bon]

i'm using phrot V0.50e and i get these on my Quad:
(after i found the correct cygwin1.dll !!!)

Actually testing 3683911104*1679616^6175-1 (6177/14336 limbs)
78959*6^49406-1 [-378311,-13669,-245232,-591674] is composite LLR64=9BEB524D57AE7AB3. (e=0.10714 (0.145629~4.83233e-16@0.961) t=93.97s)
Actually testing 37295*1679616^6177-1 (6178/14336 limbs)
37295*6^49416-1 [-706069,-134196,355894,-9704] is composite LLR64=C031190FC6BAB777. (e=0.11607 (0.145643~5.23467e-16@0.983) t=93.93s)
Actually testing 3683911104*1679616^6177-1 (6179/14336 limbs)
78959*6^49422-1 [552124,-744199,-475342,-346817] is composite LLR64=E780F540CA8CBB74. (e=0.10714 (0.145657~4.83155e-16@0.952) t=93.89s)
Actually testing 14281494912*1679616^6177-1 (6179/14336 limbs)
51017*6^49423-1 [547602,238131,-276377,-533802] is composite LLR64=52062E8F631EB963. (e=0.10714 (0.145657~4.83155e-16@0.994) t=93.91s)
Actually testing 459522720*1679616^6178-1 (6180/14336 limbs)
59095*6^49429-1 [-198072,-316970,763524,-548479] is composite LLR64=1F9762B561E67B0A. (e=0.11607 (0.145671~5.23383e-16@0.989) t=93.91s)
Actually testing 10293806592*1679616^6178-1 (6180/14336 limbs)
36772*6^49431-1 [602229,594907,-613816,781072] is composite LLR64=C1CB2E0EC887B6E4. (e=0.11242 (0.145671~5.06887e-16@0.989) t=94.00s)
Actually testing 33627*1679616^6179-1 (6180/14336 limbs)
33627*6^49432-1 [746765,-493447,-274942,-514020] is composite LLR64=4A0E3DC103F81229. (e=0.10714 (0.145671~4.83116e-16@1.321) t=94.03s)
Actually testing 2842524*1679616^6180-1 (6182/14336 limbs)
78959*6^49442-1 [318799,17268,-234287,188230] is composite LLR64=100B2D742ADA1F46. (e=0.12500 (0.145699~5.63541e-16@0.924) t=93.97s)

with LLR V3.7.1c i got about 89 seconds per test so about 5 seconds faster than phrot here!

perhaps i try to compile a version for Win (need a free C-compiler first and the source for phrot V0.51!)
karsten

[em99010pepe]

I'm gonna try once again. Where did you download the correct dll file?