-
Notifications
You must be signed in to change notification settings - Fork 7
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
Linker bug in macOS 13 beta 5 / CLT 14 beta 4 #6
Comments
yeah, that does not look like something down to us
I don't have any spare h/w at the moment to use for 13beta. |
Filed with Apple as FB11369327 |
I've been able to find a simple reproducer:
on the object file attached at https://www.dropbox.com/s/ngdjmpal0sh9zhd/basic_file.o?dl=0 |
we do invoke the linker with "no_compact_unwind", I assume? |
Yes we invoke the linker with
|
good, that indicates that the flag is honoured but the problem remains.
|
The crash is observed with:
The same command line works fine with:
|
14.0b3 seems to have |
BTW: the 13.0 SDK in 14.0b3 does not work with GCC ... has that been fixed ? (/me has not got around to d/l latest CLT yet). |
Apparently, not an Arm64-specific issue ... 14.0b3, Monterey, Intel ld64 version as above:
|
Have they again included some nonstandard construct in the headers? Do you have an example/idea of where the issue is? I can report it, but we should do it soon, so it gets fixed. |
I will d/l latest and try it .. the fail happens before the ld64 one so that's not a blocker. |
|
This same linker failure is happening on 12.6 (Monterey).
|
@lukaso which issue? SDK or linker crash? |
The linker bug is present in the released Xcode 14:
|
Linker bug. [Updated my comment above.] |
I don't understand any much of it , but if someone can guide me how to get rid of this error , then that would be very helpful ! |
Even I m facing the same issue it popped for me today |
Going back for now to the previous Command Line Tools for Xcode 13.4 (or full Xcode if you need that, but I didn't try it), which can be downloaded from Apple here (note: free Apple Developer account required), did it for me. |
The same "fix" sorts out PR106961, at least on x86_64 - aarch64 to be tried later! |
Hey i have installed the Command Line Tools for Xcode 13.4 from Apple. Till now i haven't got the error yet , but if it happens i will inform you here brother. |
Hit this myself today. Does anyone know if 14.1 Beta fixes this issue? I'm trying to work out the right request for my admins, i.e., "Downgrade XCode" vs "Upgrade XCode". Or can I keep XCode 14 (I don't do any apple development, just have it for clang), and just install/downgrade the command line tools? |
I did try the Command Line Tools for Xcode 14.1 beta (dated Sep 14) before downgrading and ran into the same bug. Only the downgrade worked for me. |
Testes with 14.1 and I still get the error. |
@matteocorti @gerlero Dang, thanks. Can you just install 13.4 on top of XCode 14? Or do you need to go full downgrade? |
If you didn’t want to downgrade both, you could probably do
(maybe only need |
please help me, i am using vscode and having this error?(m2 air macbook air) |
Please see the comments above #6 (comment) |
clang-15 doesn't work, boost is failing to build with "error: builtin __has_nothrow_assign is deprecated; use __is_nothrow_assignable instead [-Werror,-Wdeprecated-builtins]". clang-8 works on Mac OS 12 but not in Mac OS 10 and 11. Switching to clang-9 in those. gcc doesn't work on Mac OS 13 ATM due to iains/gcc-12-branch#6, so I disabled it there (relying on the CI tests with Mac OS 12 instead).
Due to iains/gcc-12-branch#6 (comment) g++ with XCode CLT 14.0.0 doesn't work.
We now test AppleClang 14 on Mac OS X 12. Due to iains/gcc-12-branch#6 (comment) , we test g++-11 on Mac OS X 11 till the XCode CLT issue is fixed github's side
I'm on Xcode 14.1, and have the issue with |
I have just built gcc-12.2-pre-r1 and current gcc-master (on aarch64-darwin21 [arm64 macOS 12]) using XC 14.1 command line tools, without any problems. As far as I can tell, the linker bug is fixed there [and in the 14.1RC, in fact], so you will need to analyse your problem and provide some more details. |
Just installed Xcode 14.1 command line tools and re-installed gcc-12 from homebrew. This error is still present
|
@WildUtah please file an issue at Homebrew with a full report (source compiled, exact command line, etc) |
is there any insight here? (my builds are working). |
Does CLT 14.2 fix this issue? |
@ilg-ul Supposedly it should (I've read |
hmm.. I cannot repeat this (it does not seem to be a GCC issue anyway, but...) output of |
Actually, I'm confused... I installed |
No, Xcode 14.2 and CLT 14.2 both come with |
Go figure... Alright, thanks! That explains. |
So, to be sure I got it right, the linker in Xcode/CLT 14.2 still trows this assert, for example when compiling |
@ilg-ul No, it was just me not understanding the versioning game Apple plays. So I was still running |
i think this is all ancient history now. |
While bootstrapping gcc-12.2-pre-r1:
I'll have to find some time and file a report with Apple 😢
The text was updated successfully, but these errors were encountered: