-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
a question #2
Comments
I'm not sure what you're asking. You can build a binary for either 32-bit or 64-bit but not both. But a 32-bit binary will run on both i386/x86_64.
|
Hi! bash-3.2# make CC="gcc -m32" |
to follow up.. I am on Mac OS X |
Worth noting that CPUID's behavior won't be predictable on Mac OS X because they do not expose any thread affinity APIs (that's what the compiler warnings in threads.c are about -- those functions aren't actually implemented). Why is it you're trying to do a 32-bit build on OS X, anyway? There were very few 32-bit Intel Macs released, and I believe they're unsupported these days. Assuming you have the build environment for it you could do something like CC="gcc -arch i386 -mmacosx-version-min=10.6", but I don't know how your build environment is set up. |
I am trying to build for my older Macs which i believe are still x32. Thank You so much tycho |
Please note that "x32" is something entirely different -- the term you are looking for is "x86-32" or just "x86". Let me know if you succeed. |
how to compile to support both i386 & x64bit?
Thanks
The text was updated successfully, but these errors were encountered: