On Sat, Nov 16, 2019 at 4:33 AM Hans Åberg <[email protected]> wrote:
> > > On 16 Nov 2019, at 10:14, Torbjörn Granlund <[email protected]> wrote: > > > > There is a non-zero probability that these GMP test suite failures are > > caused by bugs in GMP. We cannot tell for sure, as we have not isolated > > the failures. > > Or maybe just the test suite, as suggested som other post?! > > > And as gdb no longer > > works on Macos, I would feel like a beginner programmer again. > > There is “native” lldb, which should work with GCC, too, I think. > Just to be clear, the 'gcc' on recent macOS has always been stub binary that points to Apple's clang compiler and not gcc. Apple hasn't shipped an actual gcc based compiler since before Xcode 5.0. Jack ps The gmp package in MacPorts relies on always building with the core2 architecture in order ship uniform packaging of gmp for all Intel based Macs. That is why everyone sees the same glitch in Xcode 11 who is using MacPorts. > I also found a way to use make style programs in the Xcode visual debugger > [1], which works for clang; for gcc there is some variable it complains > over. If somebody figures out how to set it, please let me know. :-) > > 1. https://lists.gnu.org/archive/html/help-bison/2018-10/msg00004.html > > > _______________________________________________ gmp-bugs mailing list [email protected] https://gmplib.org/mailman/listinfo/gmp-bugs
