-
Notifications
You must be signed in to change notification settings - Fork 47
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
Building cgreen-runner on MacOS no longer works since switch to libbfd #288
Comments
At least loading a fat Mach-O library generated from Apple Clang into a That means that building the |
Also a GCC-11 built And that goes both for arm64 and x86_64 compiled versions. So the only compatibility "problem" we have here is that GCC-11 does not compile for both architectures at the same time, but only for the "current" one. So back to the problem of linking with Unfortunately, I have not been able to find anything similar to |
The good news is that it is possible to compile with Apple Clang and link with the Homebrew libraries. So that's a partial win. The only drawback is that even if compiled with Apple Clang (which generates a fat binary) the linkage to the Homebrew |
Keeping this open until there is some description on how to create a fat binary and library, probably by building on both archs and combining them using Probably, by creating a fat version of relevant Homebrew libraries, Apple Clang will automatically create fat binaries and libraries of Cgreen. |
Closing this since we now (without the
|
Unfortunately MacOS is another platform that no longer makes building
cgreen-runner
possible after the replacement ofnm
bylibbfd
introduced in #255.I should have checked that before merging, after all, it was I who raised the less portable nature of the
libbfd
solution... Although I made it work for Cygwin and MSYS2...MacOS has two major "environments", native Darwin with Apple Clang, and Homebrew. For Homebrew
libbfd
seems to exist inbinutils
as per "usual", but I haven´t been able to build that yet. Also it ties us to GNU gcc. I don't yet know if the library formats are similar so that we could run a Apple Clang-compiled library with a GNU gcc-compiledcgreen-runner
. If that is not a case, we are even less portable...Add to that the fact that GNU gcc does not work reliably for arm64e, in my experience, and we have a problematic matrix of environments to handle.
The text was updated successfully, but these errors were encountered: