-
-
Notifications
You must be signed in to change notification settings - Fork 107
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
[Solved] Cross compiler toolchains for Bullseye are broken #89
Comments
I think Bullseye toolchains are broken, I'm seeing plenty of issues regarding it. I'll look into it. |
Thanks! |
@f-laurens Apparently there's a bug with GCC 10.x.x when built with Glibc 2.31 and was fixed in: https://sourceware.org/pipermail/glibc-cvs/2020q1/069150.html and committed here: https://sourceware.org/pipermail/libc-alpha/2020-May/113553.html but never was backported to Glibc 2.31 release. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@f-laurens Please wait till updated binaries are release. I'll inform you here for testing again. |
@f-laurens There were way too many bugs with both GCC and Glibc. |
This issue has been resolved in the latest Toolchains version |
The new version of the Bullseye cross toolchains indeed solves my problem. |
I am attempting to use the cross compiler toolchains for Bullseye to build Python, and the Python build 'configure' step detects that the compiler is not able to compile a simple program:
I do not have the problem when using the equivalent toolchains for Buster.
The text was updated successfully, but these errors were encountered: