GCC 13.1.0 for Apple silicon
See new GCC 13.1.0 releases for aarch64-apple-darwin (i.e. Apple silicon), both native and cross compilation to arm-eabi, here.
1 post - 1 participant
See new GCC 13.1.0 releases for aarch64-apple-darwin (i.e. Apple silicon), both native and cross compilation to arm-eabi, here.
1 post - 1 participant
If you want to build a single source file, you can say llvm-gnatmake foo.adb
and all will be well. The link is done using llvm-gcc -shared-libgcc
.
If you try building with gprbuild
(the equivalent of the above would be gprbuild --target=llvm --no-project foo.adb
), gprbuild
tries to do the link with clang -static-libgcc
, which fails because clang
doesnβt support that option.
The only way Iβve found round this is to use an actual project with
package Linker is
for Driver use "g++";
end Linker;
but does anyone know a way of saying the same thing to gprbuild
from the command line?
Why g++
I hear you ask? It looks to me as though gprbuild
would normally use a C compiler, unless it detects the faintest whiff of C++, in which case itβll use a C++ compiler, so as to be sure of getting the C++ libraries. It looks on the PATH
for a C[++] compiler thatβs compatible with the target, llvm
, and the only one it finds is /usr/bin/clang[++]
.
2 posts - 1 participant
Not that Iβm personally worried, but just saw this: Visual Studio for Mac 'retired': From open source, to closed source, to dead β’ DEVCLASS
5 posts - 4 participants
This is a release of GCC 13.2.0 for Apple silicon, including many supporting packages (AUnit, XML/Ada, Gprbuild, GNATColl, LibAdaLang).
It incorporates the Xcode 15 fix which I hope will solve problems that macOS users have been reporting with the latest Xcode/Command Line Tools releases.
2 posts - 2 participants