[QUOTE=Prime95;251804]I found my notes about how to get out of dependency hell. The 32-bit Linux version is now available!

The 32-bit version was built on Ubuntu 10.04, the 64-bit version was built on Ubuntu 10.10. If needed I can install 64-bit Ubuntu 10.04 and rebuild the 64-bit version. Just let me know if you run into glibc problems.[/QUOTE]


Ubuntu 9.10 64-bit

[code]
./mprime: /lib/libc.so.6: version `GLIBC_2.11' not found (required by ./mprime)
[/code]

:no:

Luigi

Completion percentage is certainly not right:[code][Feb 9 10:00] Waiting 5 seconds to stagger worker starts.
[Feb 9 10:00] Worker starting
[Feb 9 10:00] Setting affinity to run worker on logical CPUs 2,3
[Feb 9 10:00] Optimal P-1 factoring of M58021673 using up to 4608MB of memory.
[Feb 9 10:00] Assuming no factors below 2^70 and 2 primality tests saved if a factor is found.
[Feb 9 10:00] Optimal bounds are B1=660000, B2=16830000
[Feb 9 10:00] Chance of finding a factor is an estimated 5.62%
[Feb 9 10:00] Using Core2 type-3 FFT length 3M, Pass1=1K, Pass2=3K, 2 threads
[Feb 9 10:00] Setting affinity to run helper thread 1 on logical CPUs 2,3
[Feb 9 10:00] Available memory is 1494MB.
[Feb 9 10:00] Using 1472MB of memory. Processing 51 relative primes (384 of 480 already processed).
[Feb 9 10:05] M58021673 stage 2 is 91.868590% complete.
[Feb 9 10:19] M58021673 stage 2 is 92.737674% complete. Time: 867.268 sec.
[Feb 9 10:35] M58021673 stage 2 is 93.600987% complete. Time: 938.293 sec.
[Feb 9 10:50] M58021673 stage 2 is 94.456527% complete. Time: 900.866 sec.
[Feb 9 11:05] M58021673 stage 2 is 95.374253% complete. Time: 911.726 sec.
[Feb 9 11:20] M58021673 stage 2 is 96.330139% complete. Time: 912.869 sec.
[Feb 9 11:35] M58021673 stage 2 is 97.283906% complete. Time: 926.810 sec.
[Feb 9 11:51] M58021673 stage 2 is 98.237672% complete. Time: 945.193 sec.
[Feb 9 12:06] M58021673 stage 2 is 99.200625% complete. Time: 883.005 sec.
[Feb 9 12:21] M58021673 stage 2 is 100.000000% complete. Time: 883.203 sec.
[Feb 9 12:35] M58021673 stage 2 is 100.000000% complete. Time: 872.055 sec.
[Feb 9 12:47] Available memory is 1476MB.
[Feb 9 12:47] Using 1326MB of memory. Processing 45 relative primes (435 of 480 already processed).
[Feb 9 12:49] M58021673 stage 2 is 100.000000% complete. Time: 844.224 sec.
[Feb 9 13:04] M58021673 stage 2 is 100.000000% complete. Time: 882.639 sec.
[Feb 9 13:19] M58021673 stage 2 is 100.000000% complete. Time: 873.327 sec.
[Feb 9 13:33] M58021673 stage 2 is 100.000000% complete. Time: 880.313 sec.[/code]

[QUOTE=ET_;251963]
[code]
./mprime: /lib/libc.so.6: version `GLIBC_2.11' not found (required by ./mprime)
[/code][/QUOTE]

Do you think if I download Ubuntu 10.04 and build 64-bit mprime that it will run properly on your Ubuntu 9.10 system?

Linux folks, help me out here! Why is it so hard to build one mprime executable that runs on all Linux variants? Or is it simply that I adopted the bleeding edge 10.10 release too soon?

[QUOTE=Prime95;251970]Do you think if I download Ubuntu 10.04 and build 64-bit mprime that it will run properly on your Ubuntu 9.10 system?

Linux folks, help me out here! Why is it so hard to build one mprime executable that runs on all Linux variants? Or is it simply that I adopted the bleeding edge 10.10 release too soon?[/QUOTE]

Ad 1. If the glibc versions are different and not backward compatible then problaby not.

Ad 2. I don't know if it is hard in a general sense - I'd rather say that it is hard doing it the way you do it. If I had to do it, that is to prepare a staticaly linked binary, I'd separate the build process from the actual linux distribution used. I think this can be achieved by praparing a cross-target build environment employing custom toolchain based on selected glibc/gcc/(kernel ?) combo. Of course once you make a decision on the oldest glibc version supported (which would be the baseline for your custom toolchain) it will imply a clear cut for users having older installations, but then they can always make their own builds.
I think googling for topics on cross-compilation would bring more details on that - there are many of these since the popularity of embedded deviced programming environments.
I have some printouts in the cabinet at work (and some practical knowledge regarding cross compiling), so if you don't mind waiting till tomorrow I can check them for you.
Of course I may be wrong will all the above, but then I hope someone can jump in here and correct me.

HTH

[EDIT] If the above is valid then an added value would be having two build enviroments for 32- and 64-bit binary on a single linux box.

[QUOTE=ET_;251963]
./mprime: /lib/libc.so.6: version `GLIBC_2.11' not found (required by ./mprime)
[/QUOTE]

I had an old Ubuntu 9.04 64-bit CD lying around. I installed that and built a new 64-bit mprime. Download it and give it a try.

[QUOTE=Prime95;251970]Linux folks, help me out here! Why is it so hard to build one mprime executable that runs on all Linux variants? Or is it simply that I adopted the bleeding edge 10.10 release too soon?[/QUOTE]
Because some distros Linux are the new Windows. :-) (In more ways than one. There was a time when kernels were even faster incompatible than recently.)

Idea: you could 'exec' curl calls to an external binary, and cut that Gordian knot. The users should be then instructed to have a working curl binary on their system. [Some programs do that with gzip, instead of linking to zlib.]

[QUOTE=Prime95;251979]I had an old Ubuntu 9.04 64-bit CD lying around. I installed that and built a new 64-bit mprime. Download it and give it a try.[/QUOTE]

Thanks, I'll test it as I get home tonight, if it's the actual linux 64-bit link on post #1!

Luigi

Thanks for the quick fix
 

[QUOTE=Rhyled;251745]I ran a couple of benchmarks against the new 26.5 - 64 bit Windows version today. When reviewing my benchmarks, they are reported as version 26.4 build 1
[/QUOTE]

When checking my latest benchmark, I noticed that both the Prime95 version and my clock speed are now being reported correctly. Thanks for the quick work.

glibc or not glibc
 

Is glibc a must ? If one would like to staticaly link C library into a binary (this is one of the options which could be considered for mprime to avoid problems encountered by George) then there are [URL="http://lists.busybox.net/pipermail/uclibc/2010-May/044057.html"]reports[/URL] that glibc is not necessarily the best choice. Instead, [URL="http://www.uclibc.org/"]uClibc[/URL] (or [URL="http://www.uclibc.org/other_libs.html"]other alternatives[/URL]) could be used as a C library and [URL="http://cxx.uclibc.org/"]uClibc++[/URL] as a C++ library.

RAM usage in worker window titles don't match what the worker is actually doing:

Build 2 is available.