Turn off outputIsMappableFile when building to osx-arm64 #118
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "erykoff/no-ld64-mmap-arm64"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This fixes #117.
Further investigation shows that with the newest version of cctools-port + sigtool for signing then whenever the
outputIsMappableFile=truewhich triggerswholeBuffer = (uint8_t *)mmap(NULL, _fileSize, PROT_WRITE|PROT_READ, MAP_SHARED, fd, 0);then the output binary will not work on M1 macs. This can be triggered when either (a) the file already exists, or (b) the path is explicitly specified (relative or absolute). I'm not sure why themmapoption is necessary, and everything appears to run fine turning it off (and it is off in regular usage when you target a new file without a path specified!).Is this patch still needed with https://github.com/tpoechtrager/cctools-port/tree/986-ld64-711?
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.