Обсуждение: clang and LLVM
Hi, I was wondering if there has been anyone experimenting to compile PG using LLVM/clang compiler tools. Regards, Gevik.
Gevik Babakhani <pgdev@xs4all.nl> writes:
> I was wondering if there has been anyone experimenting to compile PG
> using LLVM/clang compiler tools.
There is (or was, not sure if it's up right now) a buildfarm machine
using LLVM.
regards, tom lane
Firebird http://mapopa.blogspot.com/2010/10/clang-compiling-successful-experiments.html Regards Alexandre Riveira Tom Lane escreveu: > Gevik Babakhani <pgdev@xs4all.nl> writes: > >> I was wondering if there has been anyone experimenting to compile PG >> using LLVM/clang compiler tools. >> > > There is (or was, not sure if it's up right now) a buildfarm machine > using LLVM. > > regards, tom lane > >
On 12/17/2010 04:50 AM, Alexandre Riveira wrote: > Firebird > > http://mapopa.blogspot.com/2010/10/clang-compiling-successful-experiments.html > In addition to top-posting this has nothing to do with the original question, and is seriously off-topic for a Postgres developers mailing list. cheers andrew
On tor, 2010-12-16 at 22:31 +0100, Gevik Babakhani wrote: > I was wondering if there has been anyone experimenting to compile PG > using LLVM/clang compiler tools. This has been dealt with a number of times. Search the archives.
-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 > I was wondering if there has been anyone experimenting to compile PG > using LLVM/clang compiler tools. I got it working on Linux but it required a Postgres src file change to work properly (see previous thread by me). Supposedly the clang bug that caused this was fixed in llvm's HEAD, but HEAD will not compile for me yet, so I cannot verify it yet. There's a separate bug concerning usage of plperl, but that's for another day. - -- Greg Sabino Mullane greg@turnstep.com End Point Corporation http://www.endpoint.com/ PGP Key: 0x14964AC8 201012171144 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAk0Lk4UACgkQvJuQZxSWSsigEwCdG9aNk50eK1EzelewzqGMhgyO 8fYAoPt+emmdaxEd7lmeYidYgpqIdfjK =6ksq -----END PGP SIGNATURE-----