-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 7/4/07, Ralf S. Engelschall wrote:
As more software will have similar problems (e.g. Berkeley-DB), the best solution here IMHO is to either upgrade the 32-bit user-land to 64-bit or downgrade the 64-bit kernel to a 32-bit one. The combination you are driving calls for trouble. Alternatively you can hack the detection in GMP's "configure" script or try the "ABI" environment variable the "configure" script seems to accept. Just passing a compiler flag doesn't work as GMP selects assembly code himself during configure time.
I set the ABI to 32 in the spec file and that did the trick. I'm not worried about the 32/64 quite yet. I'm familiar with the possible problems (our production ldap is all 64-bit), but this isn't going to be for production. I'm just going to be giving this software a try and if we end up using it, it won't even be on this o/s. - -- Andy Harrison public key: 0x67518262 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: http://firegpg.tuxfamily.org iD8DBQFGjVh+NTm8fWdRgmIRAtPcAJwPh+nmKxZHAMd1GjXieMu+icpNtACfbEFQ Ofd7sEm2To5bm5kV4ltK3F8= =oBQw -----END PGP SIGNATURE----- ______________________________________________________________________ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
