User Profile

'Eskimo' provided an answer to a related question a few months ago: 'How does a C program compiled from the command line link against a library in the Big Sur dynamic library cache?' Typically, in these fora, there is a lot of rhetoric about the right and wrong ways of doing things. As a retired IT professional, I am not much interested in that. I just want to get my projects to work. Prior to Big Sur I was working on a Swift program to act as a simple IDE for Intel syntax X64 development. The user could use the app to fire up a source code editor and then compile, link and execute the resulting programs using default NASM and LD commands (or type specific commands directly into the app for execution). The Swift app would then execute the commands in Terminal and display the results. Post Big Sur and some fiddling I got the NASM commands to work again but I have tried every which way to make LD commands link the object files to the system library in order to execute system functions and cannot get beyond ‘lSystem not found’. Obviously, in this context, it is not helpful to know how to use Xcode or the C complier chain to perform such linking. Simple question, is it possible to link an X64 object file to lSystem using LD such as to produce an executable that will run in Terminal or not. I have tried, as suggested in previous answers, using the command syntax that -v offers to aid constructing the LD command line but to no avail.

I have a program that generates Nasm and LD commands and executes them via Shell. The LD commands link the X64 object file to libSystem.dylib but under Big Sur such dynamic libraries no longer seem to be present. What approach is now needed to produce X64 executables using system functions?