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
I'm trying to resolve Warnings of libc-test for a uclibc-based OS (x86_64-unknown-l4re-uclibc). Currently, I'm facing a more general issue for which I'm not sure how to fix it:
Hold off on doing any ctest changes, we'll have that in-repo soon #4283. Does ulibc use this type alias? If our definitions do match libc but ctest is causing problems, then fixing ctest is probably the best way forward.
I'm trying to resolve Warnings of libc-test for a uclibc-based OS (x86_64-unknown-l4re-uclibc). Currently, I'm facing a more general issue for which I'm not sure how to fix it:
Example:
libc/src/unix/linux_like/linux/uclibc/x86_64/mod.rs
Line 11 in e021460
Since this is a "helper type" without pendant in the uclibc, I added this to cfg.skip_type(...)
Example:
libc/src/unix/linux_like/linux/uclibc/x86_64/mod.rs
Lines 149 to 151 in e021460
Example:
=> Is there any way how to resolve this problem?
I tried adding the resolving of type aliases to ctest2:
at: https://github.com/JohnTitor/ctest2/blob/05634716fbe6f9ea4bf090ce85776269740b1a58/src/lib.rs#L1214
But this brings up new problems, e.g. that types get resolved that were not meant to be resolved, e.g.
pub type Elf32_Rel = __c_anonymous_elf32_rel;
here's the corresponding warning:
What do you think? Is...
The text was updated successfully, but these errors were encountered: