Re: MacPorts vs. Apple compiler issues, Handle

2024-03-19 Thread Riccardo Mottola via macports-users
Hi, Sergio Had wrote: Could you refer me to the beginning of this discussion please? it started on the Mac Users mailing list, you can find in the archives! I am also involved in AF project:) Oh, I am curious, how? I am essentially the only active developer currently, except Roy who

Re: MacPorts vs. Apple compiler issues, Handle

2024-03-19 Thread Riccardo Mottola via macports-users
Hi, Joshua Root wrote: (Moving to macports-dev as it is a better fit for this topic.) indeed, it is a development issue, although well, not for a MacPorts package (yet?) but use of MP development tools. Issues that only appear at higher optimisation levels also often involve undefined

Re: MacPorts vs. Apple compiler issues, Handle

2024-03-18 Thread Joshua Root
(Moving to macports-dev as it is a better fit for this topic.) On 18/3/2024 22:50, Riccardo Mottola wrote: I will do another compilation reducing the optimization level. GCC has an issue where beyond gcc6 certain optimizations need to be disabled, or AF crashes. Issues that only appear at

Re: MacPorts vs. Apple compiler issues, Handle

2024-03-18 Thread Riccardo Mottola via macports-users
Hi Joshua, Joshua Root wrote: Yes, any number of programs have had bugs that only became apparent when building with a newer compiler. But that's a very broad category, so without knowing the nature of the crash you're seeing, it's impossible to say what else might have had a similar

Re: MacPorts vs. Apple compiler issues, Handle

2024-03-13 Thread Joshua Root
On 13/3/2024 20:52, Riccardo Mottola wrote: I found a minor patch by Firefox to solve this namespace collision. So for whatever reason Apple's did differently, it now compiles on all compilers. However clang9 generates a crashing executable. I tried on both 10.11 and 10.13. - Apple clang:

Re: MacPorts vs. Apple compiler issues, Handle

2024-03-13 Thread Riccardo Mottola via macports-users
Hi, Joshua Root wrote: The version difference is less slight than you might think. Apple clang version numbers are unrelated to the version number of the llvm.org release they are based on. Apple clang 9.1.0 is closest to the clang-5.0 port. The name collision looks genuine however. I can

Re: MacPorts vs. Apple compiler issues, Handle

2024-03-10 Thread Riccardo Mottola via macports-users
Hi Joshua, Joshua Root wrote: MacPort installs: $ clang-mp-9.0 --version clang version 9.0.1 Apple: $ clang --version Apple LLVM version 9.1.0 (clang-902.0.39.1) Is there some Apple "trick" or is it the slight compiler difference in version? The version difference is less slight than you

Re: MacPorts vs. Apple compiler issues, Handle

2024-03-10 Thread Joshua Root
MacPort installs: $ clang-mp-9.0 --version clang version 9.0.1 Apple: $ clang --version Apple LLVM version 9.1.0 (clang-902.0.39.1) Is there some Apple "trick" or is it the slight compiler difference in version? The version difference is less slight than you might think. Apple clang version

MacPorts vs. Apple compiler issues, Handle

2024-03-10 Thread Riccardo Mottola via macports-users
Hi! I am wondering about differences between Apple clang and MacPorts clang. I tried to compile ArcticFox on 10.13, but in back compiatibility (10.9 target on 10.11 SDK got through MacPorts) Using exactly the same configuration options, MacPort clang 9.0 fails with: 169:29.18