Skip to content
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

Fix build failure due to libc++ using libc functions #116

Merged
merged 1 commit into from
Aug 4, 2022

Conversation

aperezdc
Copy link
Contributor

@aperezdc aperezdc commented Aug 4, 2022

Include the alloc-private.h header after the C++ standard library headers. This sidesteps build failures caused by implementations of std::map and std::string which use libc memory allocation functions in expanded templates after they have been marked with the poison pragma.

Fixes #115

@aperezdc aperezdc added bug merge:libwpe-1.12 PR should be merged to the 1.12 branch as well labels Aug 4, 2022
@aperezdc aperezdc self-assigned this Aug 4, 2022
Include the "alloc-private.h" header after the C++ standard library
headers. This sidesteps build failures caused by implementations of
std::map and std::string which use libc memory allocation functions
in expanded templates after they have been marked with the "poison"
pragma.

Fixes #115
@aperezdc aperezdc merged commit d77bc02 into master Aug 4, 2022
@aperezdc aperezdc deleted the aperezdc/fix-libcxx-build branch August 4, 2022 13:37
@aperezdc
Copy link
Contributor Author

aperezdc commented Aug 4, 2022

Cherry-picked into the libwpe-1.12 release branch as commit f1cac5b

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug merge:libwpe-1.12 PR should be merged to the 1.12 branch as well
Development

Successfully merging this pull request may close these issues.

Failed to build with libc++: attempt to use a poisoned identifier
2 participants