| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Devrim Gündüz <devrim(at)gunduz(dot)org> |
| Subject: | Re: [PATCH] Skip llvm bytecode generation if LLVM is missing |
| Date: | 2020-03-11 05:43:24 |
| Message-ID: | CAOBaU_YWbUMz6dh6L5AFunaid+V2ACJJ_zRZbc145ddKVmWV=Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Le mer. 11 mars 2020 à 05:28, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> a
écrit :
> On Wed, 2020-03-11 at 11:25 +0800, Craig Ringer wrote:
> > Short version: Currently if the server is built with --with-llvm the
> > -devel packages must depend on clang for PGXS to work, even though
> > llvm is otherwise optional. This is a particular problem on older
> > platforms where 3rd party LLVM may be required to build the server's
> > llvmjit support. Work around by skipping the default .bc generation if
> > no clang is found by PGXS, as if $(with_llvm) was false.
>
> +1
>
> I have struggled with this, as have several users trying to build
> oracle_fdw.
>
+1, I had similar experience with other extensions.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2020-03-11 05:47:10 | Re: [PATCH] Skip llvm bytecode generation if LLVM is missing |
| Previous Message | Masahiko Sawada | 2020-03-11 05:42:34 | Re: Do we need to handle orphaned prepared transactions in the server? |