Thanks everyone for their comments. > try explicitly adding "-stdlib=libc++" to CXXLAGS and LDFLAGS.
Adding these flags to the Makefile didn't change anything: the build again failed with givaro-4.1.1 > After installing Xcode, did you run Xcode? Yes, of course! Xcode and the command line tools are both fully installed, with the terms and conditions agreed. The build would fail much earlier if this was not the case. Just for fun I tried reinstalling Xcode (and the command line tools and then accepting the xcode conditions etc) but this made no difference in the sense that the sage build died at exactly the same place. Perhaps I should winding back to xcode 11? Andrew On Wednesday, 30 October 2019 11:39:18 UTC+11, Samuel Lelievre wrote: > > Tue 2019-10-29 11:46 UTC, Andrew: > > > > Thanks Dima > > > > On Tuesday, 29 October 2019 17:51:02 UTC+11, Dima Pasechnik wrote: > >> > >> Did you run > >> > >> xcode-select --install > >> > >> after Xcode upgrade? > > > > > > Yes, the command line tools are correctly installed but, as far as I can > see, > > xcode-select --install is no longer the correct way to check this > > because it results in the error: > > > > xcode-select: error: command line tools are already installed, use > "Software Update" to install updates > > It's still the correct way; the error message is for trying to install > while it's already installed. Sometimes one needs to start XCode > once, and agree to the terms and conditions. > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/5844078d-ed2a-40cc-ac52-30d92718fe1d%40googlegroups.com.
