Ok, now I have it built on an RH9.0 and an RH7.3 machine. I generate binaries from each and try them on the same machine and the other.
RH9.0->RH9.0: [EMAIL PROTECTED]:~/landman/private] 28 >pp prime2.pl [EMAIL PROTECTED]:~/landman/private] 29 >./a.out 100 pid: 16245 N=100 1 2**2 5**2 works RH9.0->RH7.3: [EMAIL PROTECTED]:~] 17 >./a.out ./a.out: /lib/i686/libc.so.6: version `GLIBC_2.3.2' not found (required by ./a.out) ./a.out: /lib/i686/libc.so.6: version `GLIBC_2.3' not found (required by ./a.out) ok, this would be fine if the 7.3 binary worked. I could live with building on an earlier architecture (reminds me of RPMs). This appears to be a library problem, and is not PAR's issue per se. Linking against newer .so's means the older platforms without them may not work. Now the RH7.3 tests (same PAR-0.70 distribution with the fix incorporated) RH7.3->RH7.3: [EMAIL PROTECTED]:~/private] 21 >./a.out 100 ./a.out: relocation error: /tmp/db6a189e.so: undefined symbol: Perl_Tstack_sp_ptr RH7.3->RH9.0: [EMAIL PROTECTED]:~] 4 >./a.out 100 ./a.out: relocation error: /tmp/db6a189e.so: undefined symbol: Perl_Tstack_sp_ptr Both machines have identically built Perl's. Any thoughts? Note: if there is a way to resolve the library issue, I would be happy. I already tried -l libc.so.6 and that did not work. -- Joseph Landman <[EMAIL PROTECTED]>
