Over time I found out that "uname -m" is not reliable.
Running #cat /proc/cpuinfo confirmed I had a 64-bit machine.
I agree, but if you factor in all the possible outputs, it's just too much for a configure script to decipher. Thats why you always see "uname -m" in the configure (or at least I can never recall a script that didn't do that).
Just the same, I had the option of using it for troubleshooting and made the mistake of folling the scripts process.
thanks for heads up on that, I'll make a note.