Difference from BrowserUks -V is presence of use64bitint=define, but HAVE_QUAD doesn't appear to depend on it.
The other difference is I'm using gcc on 32bit OS, but I have 64-bit processor, but I think it should still work :)
I'm recompiling now, will update with full -V.
update:
update: well, use64bitint=define seems to make Q/q available, and the simple test matches BrowserUks results.
update: hmm, it compiles, Q/q is available, but some failing tests, awww :)
Read more... $ perl harness op/64bitint.t op/pack.t op/sprintf2.t (15 kB)
And the other new test failures
Read more... $ perl harness ../dist/Math-BigInt/t/bare_mbi.t ../dist/Math-BigInt/t/bigintpm.t ../dist/Math-BigInt/t/sub_mbi.t (3 kB)
Oh well :) Thanks | [reply]
[d/l]
[select] |
The other difference is I'm using gcc on 32bit OS, but I have 64-bit processor
Getting proper quad and 64-bit int support for that particular mix is largely "unchartered waters", afaik. I believe it should be do-able (and do-able also with a 32-bit processor), but I know how to achieve it only with a 64-bit compiler and a 64-bit processor.
As you've discovered, there's a bit more involved than just getting %Config to report what you want it to.
Cheers,
Rob
| [reply] |