In the meantime I converted the PE/COFF files into missing ELF objects:

[CODE]objcopy -I pe-i386 r4delay_p4tp.obj -O elf32-i386 r4delay_p4tp.o[/CODE]also for [FONT=Courier New]r4delay5_p4tp.obj[/FONT] and [FONT=Courier New]r4delay3_p4tp.obj[/FONT].
Now mprime compiles in 32-bit version just fine:

[CODE]-- Build type: RELEASE
-- System Info:
SYSTEM_NAME: Linux
SYSTEM_PROCESSOR: i686
SYSTEM_VERSION: 2.6.34-gentoo-r6
-- Compiling for 32-bit system
-- Configuring done
-- Generating done
-- Build files have been written to: /home/scr2/000000000/cmake
[ 1%] Generating /home/scr2/000000000/gwnum/r4dwpn_p4tp.o
[ 2%] Generating /home/scr2/000000000/gwnum/cpuidhlp.o
[ 3%] Generating /home/scr2/000000000/gwnum/gianthlp.o
[ 5%] Generating /home/scr2/000000000/gwnum/hg_blend.o
[ 6%] Generating /home/scr2/000000000/gwnum/hg_core.o
[ 7%] Generating /home/scr2/000000000/gwnum/hg_k10.o
[ 8%] Generating /home/scr2/000000000/gwnum/hg_k8.o
[ 10%] Generating /home/scr2/000000000/gwnum/hg_p4.o
[ 11%] Generating /home/scr2/000000000/gwnum/mult.o
[ 12%] Generating /home/scr2/000000000/gwnum/r4_core.o
[ 13%] Generating /home/scr2/000000000/gwnum/r4_k10.o
[ 15%] Generating /home/scr2/000000000/gwnum/r4_k8.o
[ 16%] Generating /home/scr2/000000000/gwnum/r4_p4.o
[ 17%] Generating /home/scr2/000000000/gwnum/r4delay3_co.o
[ 18%] Generating /home/scr2/000000000/gwnum/r4delay3_k1.o
[ 20%] Generating /home/scr2/000000000/gwnum/r4delay3_k8.o
[ 21%] Generating /home/scr2/000000000/gwnum/r4delay3_p4.o
[ 22%] Generating /home/scr2/000000000/gwnum/r4delay3_p4tp.o
[ 24%] Generating /home/scr2/000000000/gwnum/r4delay5_co.o
[ 25%] Generating /home/scr2/000000000/gwnum/r4delay5_k1.o
[ 26%] Generating /home/scr2/000000000/gwnum/r4delay5_k8.o
[ 27%] Generating /home/scr2/000000000/gwnum/r4delay5_p4.o
[ 29%] Generating /home/scr2/000000000/gwnum/r4delay5_p4tp.o
[ 30%] Generating /home/scr2/000000000/gwnum/r4delay_cor.o
[ 31%] Generating /home/scr2/000000000/gwnum/r4delay_k10.o
[ 32%] Generating /home/scr2/000000000/gwnum/r4delay_k8.o
[ 34%] Generating /home/scr2/000000000/gwnum/r4delay_p4.o
[ 35%] Generating /home/scr2/000000000/gwnum/r4delay_p4tp.o
[ 36%] Generating /home/scr2/000000000/gwnum/r4dwpn3_cor.o
[ 37%] Generating /home/scr2/000000000/gwnum/r4dwpn3_k10.o
[ 39%] Generating /home/scr2/000000000/gwnum/r4dwpn3_k8.o
[ 40%] Generating /home/scr2/000000000/gwnum/r4dwpn3_p4.o
[ 41%] Generating /home/scr2/000000000/gwnum/r4dwpn5_cor.o
[ 43%] Generating /home/scr2/000000000/gwnum/r4dwpn5_k10.o
[ 44%] Generating /home/scr2/000000000/gwnum/r4dwpn5_k8.o
[ 45%] Generating /home/scr2/000000000/gwnum/r4dwpn5_p4.o
[ 46%] Generating /home/scr2/000000000/gwnum/r4dwpn_core.o
[ 48%] Generating /home/scr2/000000000/gwnum/r4dwpn_k10.o
[ 49%] Generating /home/scr2/000000000/gwnum/r4dwpn_k8.o
[ 50%] Generating /home/scr2/000000000/gwnum/r4dwpn_p4.o
[ 51%] Generating /home/scr2/000000000/gwnum/timeit.o
[ 53%] Generating /home/scr2/000000000/gwnum/xmult1ax.o
[ 54%] Generating /home/scr2/000000000/gwnum/xmult2.o
[ 55%] Generating /home/scr2/000000000/gwnum/xmult2a_cor.o
[ 56%] Generating /home/scr2/000000000/gwnum/xmult2a_k8.o
[ 58%] Generating /home/scr2/000000000/gwnum/xmult2ax.o
[ 59%] Generating /home/scr2/000000000/gwnum/xmult3.o
[ 60%] Generating /home/scr2/000000000/gwnum/xmult3a_cor.o
[ 62%] Generating /home/scr2/000000000/gwnum/xmult3a_k8.o
[ 63%] Generating /home/scr2/000000000/gwnum/xmult3ax.o
[ 64%] Generating /home/scr2/000000000/gwnum/hg_p4tp.o
[ 65%] Generating /home/scr2/000000000/gwnum/mult1.o
[ 67%] Generating /home/scr2/000000000/gwnum/mult1aux.o
[ 68%] Generating /home/scr2/000000000/gwnum/mult2.o
[ 69%] Generating /home/scr2/000000000/gwnum/mult2a.o
[ 70%] Generating /home/scr2/000000000/gwnum/mult2aux.o
[ 72%] Generating /home/scr2/000000000/gwnum/mult2p.o
[ 73%] Generating /home/scr2/000000000/gwnum/mult3.o
[ 74%] Generating /home/scr2/000000000/gwnum/mult3a.o
[ 75%] Generating /home/scr2/000000000/gwnum/mult3ap.o
[ 77%] Generating /home/scr2/000000000/gwnum/mult3p.o
[ 78%] Generating /home/scr2/000000000/gwnum/mult4.o
[ 79%] Generating /home/scr2/000000000/gwnum/mult4p.o
[ 81%] Generating /home/scr2/000000000/gwnum/r4_p4tp.o
[ 82%] Generating /home/scr2/000000000/gwnum/r4delay_p4t.o
[ 83%] Generating /home/scr2/000000000/gwnum/r4dwpn3_p4t.o
[ 84%] Generating /home/scr2/000000000/gwnum/r4dwpn5_p4t.o
Linking CXX static library libgwnum.a
[ 93%] Built target gwnum
Linking CXX executable mprime
[100%] Built target mprime[/CODE]I'm dynamically linking aganst [FONT=Courier New]libcurl[/FONT], so the output from [FONT=Courier New]ldd[/FONT] is
[CODE] linux-gate.so.1 => (0xb7744000)
libstdc++.so.6 => /usr/lib/gcc/i686-pc-linux-gnu/4.4.3/libstdc++.so.6 (0xb7631000)
libcurl.so.4 => /usr/lib/libcurl.so.4 (0xb75e5000)
libm.so.6 => /lib/libm.so.6 (0xb75c0000)
libgcc_s.so.1 => /usr/lib/gcc/i686-pc-linux-gnu/4.4.3/libgcc_s.so.1 (0xb75a4000)
libc.so.6 => /lib/libc.so.6 (0xb745d000)
libpthread.so.0 => /lib/libpthread.so.0 (0xb7444000)
/lib/ld-linux.so.2 (0xb7745000)
libldap-2.3.so.0 => /usr/lib/libldap-2.3.so.0 (0xb7411000)
librt.so.1 => /lib/librt.so.1 (0xb7408000)
libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0xb73d8000)
libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0xb732a000)
libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0xb7305000)
libcom_err.so.2 => /lib/libcom_err.so.2 (0xb7301000)
libresolv.so.2 => /lib/libresolv.so.2 (0xb72ec000)
libssl.so.0.9.8 => /usr/lib/libssl.so.0.9.8 (0xb72a7000)
libcrypto.so.0.9.8 => /usr/lib/libcrypto.so.0.9.8 (0xb7167000)
libdl.so.2 => /lib/libdl.so.2 (0xb7163000)
libz.so.1 => /lib/libz.so.1 (0xb7150000)
liblber-2.3.so.0 => /usr/lib/liblber-2.3.so.0 (0xb7143000)
libkrb5support.so.0 => /usr/lib/libkrb5support.so.0 (0xb713b000)[/CODE]

[QUOTE=NBtarheel_33;251672]What does "fixed in next release" mean? Fixed in v26.5 or not until v27?

And when will you be implementing the option for worktodo of "test only exponents guaranteed to yield Mersenne primes"? :P[/QUOTE]

In this case it means fixed in 26.5.

I'm working on your second suggestion, but it will require several years of testing on my own computers.

Works much better with regard to my complaints about workers not starting while [i]worktodo[/i] is locked and/or communicating with the server. Thanks!

[QUOTE=tichy;251674]So, what is the output of [FONT=Courier New]pkg-config --static --libs libcurl[/FONT] and what specificaly fails when attempting the build ?[/QUOTE]

pkg-config gives a big long list. Specifically, the linker complains that it cannot find libgssapi_krb5.

[QUOTE=henryzz;251693]Wasn't a static version version available for 24.14? Surely that would solve the problem for most people.[/QUOTE]

That sure would be nice, but Linux has decided some of the routines that are called can only be dynamically linked in. I'm sure there was a good reason, but I can't fathom what it might be.

Mildly interesting benchmark report error
 

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
[CODE]
Rhyled 2011-02-07 Intel Core i7 920 @ 2.67GHz Windows64,Prime95,v26.4,build 1 3620 11.05 14.39 17.57 21.29[/CODE]
Although my Results file says 26.5 as expected
[CODE]
Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
CPU speed: 3801.14 MHz, 4 cores
CPU features: Prefetch, MMX, SSE, SSE2, SSE4
L1 cache size: 32 KB
L2 cache size: 256 KB, L3 cache size: 8 MB
L1 cache line size: 64 bytes
L2 cache line size: 64 bytes
TLBS: 64
Prime95 64-bit version 26.5, RdtscTiming=1
Best time for 768K FFT length: 8.07 ms., avg: 8.16 ms.
Best time for 896K FFT length: 9.96 ms., avg: 10.08 ms.
Best time for 1024K FFT length: 10.90 ms., avg: 11.05 ms.
Best time for 1280K FFT length: 14.31 ms., avg: 14.39 ms.
Best time for 1536K FFT length: 17.35 ms., avg: 17.57 ms.
Best time for 1792K FFT length: 21.18 ms., avg: 21.29 ms.
[/CODE]

It never has reported the actual clock speed at least since 25.11, but I've gotten used to that. It assumes I'm using 20x 180 rather than the actual 21x 180

I'm confused; 180*21=3780, which is very close to the 3800 reported by Prime95.

[QUOTE=sdbardwick;251750]I'm confused; 180*21=3780, which is very close to the 3800 reported by Prime95.[/QUOTE]

The value in my Results.txt file is correct (my error, it's actually 21x 181 = 3801 MHz) Somehow, that shows up as 3620 in the benchmark page (scroll my first code window to the right) and also as 3620 when I look at my CPU statistics.
[CODE]
Name CPU Model / Software GHz
[URL="http://www.mersenne.org/editcpu/?g=c87a4a4b48005bbdc12e6c1accac4af4"]Rhyled[/URL] Intel Core i7 920 @ 2.67GHz Windows64,v26.4,build 1 3.620
[/CODE]

The reporting was accurate when I used a 20x 200 multiplier, but I couldn't keep it stable at acceptable temperatures much longer than a benchmark run.

No biggie - it doesn't affect my GHz-day count one way or the other. My guess is that the calculation sees that I have turboboost enabled on the processor and deducts 1 from the multiplier even though CPU-Z reports the full 3801 while Prime 95 is running.

Hi Prime95...
Elsewhere, you suggested I try 26.4 for not getting six cores automagically recognized...I haven't been able to do that just yet...should I just jump to 26.5 and try that?

Meanwhile, six cores crunch away...real LL results in a month or so....patience, patience...

[B]Rhyled[/B], Core-i7 920 (rev.D0) running rock-solid at 20*200 at my place (crashes instantly, if I enable TurboBoost and it switches on). I'm using the ThermalRight U120 AirCooler.
Although, some reviews state an opinion, that by rising 185->200 on BaseClock, we increase the power consumption by 50%...

[QUOTE=Christenson;251760]Elsewhere, you suggested I try 26.4 for not getting six cores automagically recognized...I haven't been able to do that just yet...should I just jump to 26.5 and try that?[/QUOTE]

Go straight to 26.5 unless you're using Linux 32-bit. I hope to get that built tomorrow.