hfsinspect: src/crc32c/crc32c.c:29:13: error: instruction requires: Not 64-bit mode

Ken Cunningham ken.cunningham.webuse at gmail.com
Tue May 5 16:07:12 UTC 2020

On 2020-05-05 8:43 a.m., Paul de Vries wrote:
>> On 2020-05-05, at 15:49, Ken Cunningham <ken.cunningham.webuse at gmail.com> wrote:
>> you are building a 64 bit executable, but trying to include 32 bit Intel asm, which won't work.
>> hopefully there is 64 bit asm somewhere you should include instead, or some #define to set for 64 bit builds, or some way to turn off the asm, or ... some other way to not include 32 bit asm in a 64 bit build.
>> K
> OK, imagined something like that. have done many assemblers for many architectures but never intel.
> BUT, how is it possible that a manual compile works with the same code that doesnt work in macports?

For that answer, you'd have to look closely at the build lines. Perhaps 
it's building in 32bit mode when you do it manually. Maybe MacPorts is 
setting the environment up for you with lots of added bits that aren't 
happening with a manual build. Or some other reason we can't guess.

Letting Xcode do your build is usually more of a "black box" -- it is 
controllable, but very different than make or cmake or meson or any 
other build system. The configure arguments are hard to find, but there 
are a few online sites where they are all listed. The Xcode build 
usually works on an Xcode build system of the vintage of the xcode 
project, and any significant deviation from that (+/- 2 years, say) is a 
total crap shoot. So if there is an alternative, that is what I use. 
There is also a nice project I added to MacPorts a while back that 
converts an xcode project into cmake, and I will use that sometimes 
rather than manhandle an xcodebuild that doesn't want to build for me.


More information about the macports-dev mailing list