Magnus Ihse Bursie
Magnus Ihse Bursie
We currently require clang 3.5 (when building on linux I presume; Xcode has their very own peculiar way of versioning clang). Maybe this is too old? Should we instead raise...
Yeah, clang 5.0 was released in 2017. I'd recommend you just hard-code in the dwarf flags and instead apply this: ``` diff --git a/make/autoconf/toolchain.m4 b/make/autoconf/toolchain.m4 index adb4e182dcc..e1c097916d8 100644 --- a/make/autoconf/toolchain.m4...
If is is a big change or not depends on how it affects builds on macos. I assume that clang functionality that was published in 2017 is already incorporated in...
I've verified that the environment variables are properly set. I don't know what else to test. Do you have any suggestions?
If you redo `/integrate`, I can sponsor.
So enabling the warning actually exposed a bug? That's always nice to see, and a good argument for keeping up with the hygiene work of minimizing the amount of disabled...
> Also: this patch is Linux-only. I'll ask for help from build experts to make the tests GCC-only; it's not clear to me how. @theRealAph We currently have a more...
So you want to provide this dlopen wrapper for other platforms as well?
I agree that `configure` should detect and enforce build requirements. However, this is done in the wrong place. At the very least it should move to `make/autoconf/configure` as Erik says....