On 23/04/18 18:35, Andres Freund wrote:
Hi,
On 2018-04-23 18:33:30 +0300, Heikki Linnakangas wrote:
To add to the story: I installed clang 3.9, but I still got the same error.
I now had both clang 3.8 and 3.9 installed, but /usr/bin/clang still pointed
to clang-3.8, so autoconf still picked
Hi,
On 2018-04-23 18:33:30 +0300, Heikki Linnakangas wrote:
> To add to the story: I installed clang 3.9, but I still got the same error.
> I now had both clang 3.8 and 3.9 installed, but /usr/bin/clang still pointed
> to clang-3.8, so autoconf still picked that up. Only after removing
>
On 23/04/18 18:28, Andres Freund wrote:
Hi,
On 2018-04-23 04:33:04 -0400, Heikki Linnakangas wrote:
So, I have LLVM 3.9 installed, but no clang 3.9. Only clang 3.8.
Any specific reason, or just happenstance?
Just happenstance. I had clang and llvm 3.8 installed previously. But
PostgreSQL
Hi,
On 2018-04-23 04:33:04 -0400, Heikki Linnakangas wrote:
> So, I have LLVM 3.9 installed, but no clang 3.9. Only clang 3.8.
Any specific reason, or just happenstance?
> Googling around, the LLVM bitcode format is supposed to be compatible across
> versions, but I'm not sure I trust that.
On Monday, April 23, 2018 10:33:04 AM CEST Heikki Linnakangas wrote:
> Hi!
>
> I tried compiling with --with-llvm on my laptop, and got this:
> > $ make -s
> > All of PostgreSQL successfully made. Ready to install.
> > $ make -s install
> > Invalid Summary Block: version expected
> > error: can't
Hi!
I tried compiling with --with-llvm on my laptop, and got this:
$ make -s
All of PostgreSQL successfully made. Ready to install.
$ make -s install
Invalid Summary Block: version expected
error: can't create ModuleSummaryIndexObjectFile for buffer: Corrupted bitcode
#0 0x7fbe98032085
