-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Failure to build on recent versions of libc++ / clang #1536
Comments
To check this try building the toolchain using the latest upstream GCC sources from the
Unfortunately, it seems that few, if any, of the people who regularly contribute to Note that a PR to bump |
Actually, according to this thread: the fix was backported to various minor versions of GCC 13 so maybe your problem is different and not fixed by this? |
I can't speak for GCC 13 but I've just compiled the toolchain with
In other words, that fixed it. I presume then that once #1531 is merged the above will no longer be necessary? |
Thanks - that's interesting and useful feedback.
Correct.
So it looks like the fix was backported to GCC 13.3 (and maybe also 13.2.1 but I can't seem to find a branch/tag for that specific version):
If you had the time maybe the following would be worth trying...
But if you don't have time don't worry about it given that the eventual imminent (hopefully!) merging of #1531 will address the issue. |
I can confirm that GCC 13.3 works too, after building it in the described manner:
Thanks for all your help. |
That's great - thanks for checking. I'll close the issue since it's now understood. |
I am attempting to build the newlib toolchain as per the README, with the default toolchain on macOS 14.6.1 (Sonoma):
I have attempted to build the project as so:
Unfortunately, various errors occur, all similar to this:
full error output.txt
I believe this bug is already well-documented on GCC's bugzilla here and has already been fixed in mainline GCC, though I could be mistaken.
The text was updated successfully, but these errors were encountered: