You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
libc defines prop_info for Android, as an opaque type but one whose size presumably matters (since libc fills in fields to match its size). However, Android appears to have changed the size of the private fields: name is now a 0-length array at the end.
This structure doesn't seem to ever be handled by value, only by pointer, so I don't think we need to specify its private fields at all.
The stability policy for libc is not as strict as the standard library since it is intended to mirror an upstream API: if the upstream API changes then it we should mirror that change in libc. I don't think there is any sane way to manage API evolution otherwise.
Activity
Amanieu commentedon Jul 12, 2022
The stability policy for libc is not as strict as the standard library since it is intended to mirror an upstream API: if the upstream API changes then it we should mirror that change in libc. I don't think there is any sane way to manage API evolution otherwise.
joshtriplett commentedon Jul 12, 2022
In this context, though, I think we don't need the structure to have a size.
Android's prop_info type fix.
Android's prop_info type fix.
tgross35 commentedon Jun 24, 2026
I thought this was breaking but it's not, so somebody can just put up a PR whenever updating the struct definition to match sources.
If extern types were better supported then we would probably use them way more, but I don't think it's worth that change for the single case here.
android: make `prop_info` an extern type
android: make `prop_info` an extern type
android: make `prop_info` an extern type