-
Notifications
You must be signed in to change notification settings - Fork 90
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
Linux and FreeBSD Discrepancies Compiled Bug List #79
Comments
This comment has been minimized.
This comment has been minimized.
|
|
Addressed all currently listed issues in the new v0.5.1 test branch. Branch needs more testing before merge to master and minor release. This issue will also remain open for any other issues that have been missed / yet to be discovered (which I'm sure there are). |
EDIT: the constants are fixed in v0.5.1, but not in musl's internal headers. This causes musl-internal usage of these constants to fail. |
Ugh yeah that's a good point that I somehow missed. |
The |
Newly built musl-headers including @sleirsgoevy's changes and my previous changes have now been committed to the master branch after testing and confirmation of working across multiple samples. Tomorrow I'll test the TLS fix also shipped by @sleirsgoevy and if they're confirmed working, that + the issues from this thread will land in a v0.5.1 release shortly. v0.5.1 branch has been deprecated. |
Another disrepancy: signal numbers are different on FreeBSD and on Linux. |
I'm not sure if we're only doing Linux vs FreeBSD differences in this thread. Anyway there are some PS4 specific differences in the typedefs. Some conform with FreeBSD but not all do. For example on the PS4 Another one I saw was for |
|
|
Also |
ptrace PT_* constants have Linux numeric values, should have BSD ones instead. |
Gonna try to get |
This issue will be a master thread for all Linux and FreeBSD discrepancies in the headers, such as macros, constants, structure defs, type defs, and function prototypes. Please keep all discrepancies in here instead of making new issues so they're easier to track and maintain. Other related issues will be pulled into here and closed.
As this is likely an issue that will take a long time to fully address over the course of multiple updates, it will have no milestone / target release version except 1.0 stable.
--
Headers that need updating:
Areas/broader topics that need updating:
The text was updated successfully, but these errors were encountered: