Cannot install emacs on Sonoma, fails while building clang-14

Hi… CAn’t seem to figure this out. Prebuilt binaries are not yet available so macports is building from source. Looking at the output, make fails with numerous errors generated, mostly related to llvm sanitizer. Thank you. Diego Vicioso. Email… viciosodi...@icloud.com

Re: Building Clang 8/9 in El Capitan

typo, of course. I meant compiler.cxx_standard 2017 compiler.thread_local_storage yes I'm typing this in TenFourFox right now on Tiger ;> K On Sat, Feb 13, 2021 at 3:25 PM Ken Cunningham < ken.cunningham.web...@gmail.com> wrote: > To try to make bootstrapping clang and llvm as workable as

Re: Building Clang 8/9 in El Capitan

To try to make bootstrapping clang and llvm as workable as possible, the compilers that can build them are carefully tested and the portfile tweaked to manage each one. Sometimes the compilers seem to build them, but the products don't work properly. Sometimes they don't build at all. MacPorts

Re: Building Clang 8/9 in El Capitan

On Feb 13, 2021, at 03:42, Ken Cunningham wrote: > Thread local includes __thread, Thread_local, and thread_local. > > The compilers that support them are all different. > > To make it easy for people to not think about it much, especially when you’re > not talking about bootstrapping

Re: Building Clang 8/9 in El Capitan

> On Feb 13, 2021, at 1:27 AM, Ryan Schmidt wrote: > > > I would consider it unreasonable to ask users to be aware of the existence of > our buildbot infrastructure or what versions of Xcode we have installed on > the buildbot workers and to ask them to duplicate it. > > I didn't mention

Re: Building Clang 8/9 in El Capitan

On Feb 13, 2021, at 03:03, Ken Cunningham wrote: > I would suggest you install Xcode 8.2.1 to match the buildbots. > > > Don’t forget that in almost all cases, MacPorts will use the SDK installed in > “/“ when building software. That SDK is the 10.11 SDK, so it is the one that > matches

Re: Building Clang 8/9 in El Capitan

I would suggest you install Xcode 8.2.1 to match the buildbots. Don’t forget that in almost all cases, MacPorts will use the SDK installed in “/“ when building software. That SDK is the 10.11 SDK, so it is the one that matches your system, and is the one you want. Virtually all standard “open

Re: Building Clang 8/9 in El Capitan

cc8, gcc7, gcc6, etc. The problem I am having is > that it seems each of the gcc versions that OpenBLAS can be built with > ultimately have a runtime dependency on libgcc10, which wants to be built > with clang-9.0. > > Building clang-9.0 fails because the clang supplied by Xco

Re: Building Clang 8/9 in El Capitan

, gcc7, gcc6, etc. The problem I am having is that it seems each of the gcc versions that OpenBLAS can be built with ultimately have a runtime dependency on libgcc10, which wants to be built with clang-9.0. Building clang-9.0 fails because the clang supplied by Xcode 7.3 doesn't support thread

Re: Building Clang 8/9 in El Capitan

Both clang-8.0 and clang-9.0 having been building properly for us on the buildbots and (when I last did it) locally for me, on ElCap. See and the one for clang-8.0. But your logic is flawed about why you want it, as no clang version provides

Building Clang 8/9 in El Capitan

, the build failed because the clang provided by Apple in Xcode 7.3 doesn’t support thread local storage. So I figured I’d try building clang-8.0 and then I could specify to MacPorts to use that compiler to build clang-9.0. But building clang-8.0 failed as well. This time there isn’t a helpful error

Re: building clang

On Jan 18, 2021, at 19:38, Tom wrote: > how can I build clang with -ilocal option support in order to build CrossOver > Wine for 32on64? That's an option that Crossover added to clang. When I last looked into the issue last year, you had to use Crossover's special version of clang, which

building clang

Hi, how can I build clang with -ilocal option support in order to build CrossOver Wine for 32on64? Regards