Re: upcoming API changes for LLVM 12
От | Tom Lane |
---|---|
Тема | Re: upcoming API changes for LLVM 12 |
Дата | |
Msg-id | 1901328.1604874920@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: upcoming API changes for LLVM 12 (Andres Freund <andres@anarazel.de>) |
Ответы |
Re: upcoming API changes for LLVM 12
|
Список | pgsql-hackers |
Andres Freund <andres@anarazel.de> writes: > On 2020-11-02 10:28:33 -0800, Jesse Zhang wrote: >> On Thu, Oct 15, 2020 at 6:12 PM Andres Freund <andres@anarazel.de> wrote: >>> There will be a breaking API change for JIT related API in LLVM >>> 12. seawasp, which runs some bleeding-edge version of clang, has been falling over for the last couple of weeks: /home/fabien/clgtk/bin/clang -Wno-ignored-attributes -fno-strict-aliasing -fwrapv -O2 -D__STDC_LIMIT_MACROS -D__STDC_FORMAT_MACROS-D__STDC_CONSTANT_MACROS -D_DEBUG -D_GNU_SOURCE -I/home/fabien/clgtk/include -I../../../../src/include -D_GNU_SOURCE -I/usr/include/libxml2 -flto=thin -emit-llvm -c -o llvmjit_types.bc llvmjit_types.c llvmjit.c:21:10: fatal error: 'llvm-c/OrcBindings.h' file not found #include <llvm-c/OrcBindings.h> ^~~~~~~~~~~~~~~~~~~~~~ 1 error generated. I suppose this is related to what you are talking about here. If so, could we prioritize getting that committed? It's annoying to have the buildfarm failures page so full of this one issue. regards, tom lane
В списке pgsql-hackers по дате отправления: