[Bug target/106961] Testsuite failures after Command Line Tools update to v14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106961 Iain Sandoe changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #7 from Iain Sandoe --- closing as invalid - because it is not a GCC bug, and now we have a newer CLT that works.
[Bug target/106961] Testsuite failures after Command Line Tools update to v14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106961 --- Comment #6 from simon at pushface dot org --- Installing the Command Line Tools 14.1 beta 3 fixes this problem.
[Bug target/106961] Testsuite failures after Command Line Tools update to v14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106961 --- Comment #5 from simon at pushface dot org --- I used the feedback app to submit FB11552589; as a first-timer I’m unsure whether I’ve done it right.
[Bug target/106961] Testsuite failures after Command Line Tools update to v14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106961
--- Comment #4 from Iain Sandoe ---
(In reply to simon from comment #3)
> Problem still present in Xcode 4.1beta.
>From a GCC perspective, what's needed is:
* for someone to file a radar with Apple ("feedback" they are called now)
[https://feedbackassistant.apple.com]
* If it is acknowledged as an Xcode bug, and we have no way to work around it,
then we will just need to document that certain versions of Xcode are not
usable.
* If the outcome of the FB is that the problem is determined to be with GCC,
then we will have to address it.
As of now, it's not clear to me that this is a GCC bug - removing a symbol from
the library looks like an ABI break.
[Bug target/106961] Testsuite failures after Command Line Tools update to v14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106961 --- Comment #3 from simon at pushface dot org --- Problem still present in Xcode 4.1beta.
[Bug target/106961] Testsuite failures after Command Line Tools update to v14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106961 --- Comment #2 from simon at pushface dot org --- For the moment, installing Command Line Tools version 13(.4) fixes this problem (people using Xcode need to revert that). I guess the long-term solution will depend on whether the missing libunwind component is deliberate or an oversight on Apple’s part.
[Bug target/106961] Testsuite failures after Command Line Tools update to v14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106961 --- Comment #1 from Andrew Pinski --- Sounds like you should report this to Apple ...
