Closed egvijayanand closed 1 month ago
Hi I'm an AI powered bot that finds similar issues based off the issue title.
Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!
Note: You can give me feedback by thumbs upping or thumbs downing this comment.
It builds successfully on .NET 8. The issue is only with .NET 9.
can you do a find in /usr/share/dotnet/packs/Microsoft.Android.Sdk.Linux/35.0.0-rc.1.80/tools/
and look for libZipSharpNative
?
If it is there. can you run ldd
on it and make sure it has all its dependencies.
ah there it is. /lib/x86_64-linux-gnu/libc.so.6: version
GLIBC_2.33'` your libc is not up to date or does not match.
ah there it is.
/lib/x86_64-linux-gnu/libc.so.6: version
GLIBC_2.33'` your libc is not up to date or does not match.
So what's the resolution? And which one to update?
@egvijayanand what Linux distribution do you use?
@egvijayanand: Please see also: https://github.com/dotnet/runtime/blob/main/docs/design/features/y2038.md
https://github.com/dotnet/android-libzipsharp uses time_t
based members, and to begin addressing the Year 2038 Problem, it now assumes 64-bit time_t
values. The use of 64-bit time_t
values requires a newer GLibC.
If at all possible, update your Linux distribution to something that uses 64-bit time_t
values.
Have upgraded my Ubuntu from ver. 20.04 to ver. 22.04. Then the build issue was resolved.
Thanks for your support. This ticket can be marked as resolved.
Description
Android app is not building on Linux - .NET MAUI RC1.
Ends up with some weird error message.
Steps to Reproduce
Link to public reproduction project repository
Default template itself is suffice, no authored code
Version with bug
9.0.0-rc.1.24453.9
Is this a regression from previous behavior?
Yes, this used to work in .NET MAUI
Last version that worked well
9.0.0-preview.6.24327.7
Affected platforms
Android
Affected platform versions
Android 35.0
Did you find any workaround?
Nope.
Relevant log output