Skip to content

Conversation

lunkwill42
Copy link
Member

These typedefs should allow CFFI to figure out by itself which integer types are used for struct timeval members on the target platform.

Fixes #2 (maybe, I'll let @he32 test it first)

These typedefs should allow CFFI to figure out by itself which integer
types are used for struct timeval members on the target platform.
@lunkwill42 lunkwill42 self-assigned this May 13, 2025
@lunkwill42 lunkwill42 requested review from a team and he32 May 13, 2025 11:52
Copy link

🦙 MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Warnings Elapsed time
✅ PYTHON isort 6 0 0 0.34s
✅ PYTHON ruff 6 0 0 0.22s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by OX Security

Base automatically changed from bugfix/project-meta to master May 13, 2025 11:58
@lunkwill42
Copy link
Member Author

@he32 has tested on NetBSD and it appears to work for him; NetBSD/pkgsrc-wip@900772a

@lunkwill42 lunkwill42 marked this pull request as ready for review May 14, 2025 12:38
Copy link

@stveit stveit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From what I can find online it does seem like typedef int... should solve this

@lunkwill42 lunkwill42 merged commit 6e3c54b into master May 15, 2025
2 checks passed
@lunkwill42 lunkwill42 deleted the bugfix/portable-struct-timeval branch May 15, 2025 13:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Non-portable definition of "struct timeval"

2 participants