Thank you, Ryan, for going the extra mile (or two) to follow up on my posting to the Ada Forum regarding the linkage failure.
In general, I'm seeing various behavior: 1. warnings, no library or executable created; (Ada, and originally, Pluto); 2. no warnings, bogus library created (speculative on the bogus, but in this case, the Pluto libary code refuses to load the created binding from gcc); 3. no warnings, executable created and executes without problem (this is from clang++); I'm hoping that all of these cases are resolved by the gcc bug report your provided from your research. This, of course, will require a new Ada GNAT tool chain release, correct? Thanks, Ken Wolcott On Thu, Sep 25, 2025 at 5:35 PM Ryan Carsten Schmidt < [email protected]> wrote: > On Sep 24, 2025, at 16:46, Kenneth Wolcott wrote: > > > > What is the correct manner to tell the linker what it needs to know? > > I found the thread on the ADA forum where you asked the question so I > provided what I hope is the answer over there: > > > https://forum.ada-lang.io/t/gnat-toolchain-now-broken-after-os-upgrade-to-macos-26-tahoe-arm64/3843/17 > > Which boils down to giving gnatnake this flag: > > -Wl,-syslibroot,"$(xcrun --sdk macosx --show-sdk-path)" > > >
