-
Notifications
You must be signed in to change notification settings - Fork 293
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
Failed to build in Apple Silicon under macOS Monterey #259
Comments
I figured out the first compiling issue. There is a file I thought AFPS is case sensitive. Why it can't differentiate the file UPDATE:
|
This is a new compilation road block.
In
|
Refer my fork. |
@kanjitalk755 |
Hi @kanjitalk755, I deep dive into AARCH64 assembly and Mac OS mach exception mechanism. Your AARCH64 change may not be an ideal solution in AARCH64.
I ported a mach exception example code from Mr Sing's Mac OS X internal book to AARCH64. I used the same approach when BAD ACCESS Exception is thrown, do PC+=4. If the exception happens after any AARCH64 branch instruction like BLR, BR and etc, you are unlikely to recover by do PC+=4. Here is the test case. My comments on this issue. There is no easy solution to this kind of the problem. I think if we can notify the guest OS and let them handle it gracefully, it would be much better than skip an instruction. Any thoughts? |
Certainly, it cannot be handled when the branch destination is an execution prohibited page.
Instead of relying on host-side exception handler, you may need to implement the guest hardware strictly so that the guest OS handles it properly. |
Good question. The generated C codes in For the exception handler, I will bring up cmon to see why. But sometimes it is hard to figure out. I will just let it go. In my physical MacSE, I saw A bomb for read access violation. Maybe we could drop A bomb like this rather than skip the instruction? |
I observed writes to invalid addresses in a normal boot sequence of BII/SS. |
I got my Mac Studio today. Finally I could build BII under Apple Silicon with the latest Mac OS.
However, I failed to build the master branch 6393d14.
The first roadblock is outdated autoconf. It seem low hang fruits to fix (or simply ignore) all warnings by running autoupdate on configure.ac and *.m4 files. Running configure seems to look happy.
Then the actual build got stuck in slip. I have no clues why slirp was included in the build by default. I thought slirp is not 64bit ready. Therefore, it was excluded.
Maybe configure was broken in Apple Silicon?! But I did a BII build in AARCH 64 under Linux. It works.
Question:
The text was updated successfully, but these errors were encountered: