-
Notifications
You must be signed in to change notification settings - Fork 38
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
arm64 build fixes #957
base: master
Are you sure you want to change the base?
arm64 build fixes #957
Conversation
Co-authored by: [email protected]
You put WAY too many packages in one PR which is why they aren't getting accepted, it's too much to review. both db53 and db60 are too complex, you only need to add one line to db60 and change one line on db53, that's all, they both need to be forced to use |
I do approve the nettle7 fix though, just waiting on @nieder to approve it since it's his package. |
Perhaps |
Because our maintainers are thoughtful enough to document their hackery:
|
I had already seen that note, but I still think it was just the first one found, likely by griping for x86_64. I still think Darwin/_spin_lock_try is the correct answer here. |
I agree that having a bunch of unrelated files in a single PR can get confusing, since a bunch of us are working on them or also in other PRs, and no need to wait to push it as a single set.
|
I did not see what was still in the works at the time; to avoid more duplicate work wanted to push at least the draft here so others can see what is already in development. It's probably best to keep this as a tracker now that packages are being updated in their own PRs. |
Have you tested cario with older dpkg? I've like to commit that one if it's working with dpkg 1.10 |
You mean |
none of the pkg-config changes are required anymore, I fixed pkg-config tonight, selfupdate and pkg-config will start working. |
Why is |
I just haven’t had time to move it from my exp since dpkg 1.15+ was accepted and it’s low priority since we don’t have a bindist atm |
config.guess updates as required, some additional build patches; pushing now what I've come across so far to keep people from duplicating efforts.