cmake: make the glibc file offset great again#1990
Merged
Conversation
Member
|
LGTM If this is supposed to be important, it would be a good thing to have a unit test for. Maybe you could have a 10 byte file (opened with |
Member
Author
|
Some unit tests would be welcome, but I caught it because the compilation entirely failed. It may depend on default configuration on some distros, or on the way some headers are included if a dependency already sets the flag in some way or another. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I'm surprised the CI didn't catch it, that's a minor regression from me missing a rewrite after the porting to Yokai.
This affects
linux-i686where we need to assume such file stuff size is 64-bit whatever the architecture.