-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TRACKING] glibc 2.36 (and gcc 12) build failures #39960
Comments
does the recent update to |
yes, thanks for the comment |
The problem lays with mk-configure has a tendency to do its work only when it was built with a compiler of the corresponding version. If built with GCC 10.2, it looks for If used with GCC 12.2 without getting rebuilt first, the utility looks for Build failure with GCC 12 on musl (x86_64-musl): mk-configure revbump + rebuild with GCC 12: Now runawk builds as expected: |
glibc upstream has been updated to solve this... void should be using that. |
@wael444 Do you have some more information about this? Solve what exactly? This looks like a problem with the mk-configure package that we should revbump. |
https://vasilek.cz/logs/gcc12-glibc-filtered/bad/toybox.txt fixed by: just try this for glibc, some of the packages would succeed to compile |
Thanks. |
cpp-hoconSince I was not able to find Michal's logs about this package, I may include this one: cpp-hocon_fail.txt Errors clearly indicate that
This problem persists with musl-based environment the same way, too. |
|
done |
https://vasilek.cz/logs/gcc12-glibc-filtered/bad/
These are new failures from a gcc 12 glibc 2.36 world rebuild, this list doesn't include failures already found in previous musl rebuilds (#39809, #39083). These can be caused by glibc 2.36 or gcc 12 if they are not available on musl.
fixed by rebuilding mk-configure
fixed by using the glibc stable release branch instead of the 3.36 release
The text was updated successfully, but these errors were encountered: