Re: Header checking failures on LLVM-less machines
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2019-01-29T01:21:49Z
Lists: pgsql-hackers
Andres Freund <andres@anarazel.de> writes: > On 2019-01-28 19:51:22 -0500, Tom Lane wrote: >> I propose that we should fix this by making the whole bodies of those >> two headers be #ifdef USE_LLVM. > Hm, I think it's sufficient that we error out if llvm was configured, > we've sufficient buildfarm machines running with it enabled. That is not the point. The point is that you've broken a developer tool. I don't really care whether cpluspluscheck would work on some subset of buildfarm machines --- what I need is for it to work on *my* machine. It is not any more okay for the llvm headers to fail like this than it would be for libxml- or openssl- or Windows-dependent headers to fail on machines lacking respective infrastructure. (And yes, I realize that that means that cpluspluscheck can only check a subset of the header declarations on any particular machine. But there's no way around that.) regards, tom lane
Commits
-
Fix LLVM related headers to compile standalone (to fix cpluspluscheck).
- 6a5c0bb6abbf 11.2 landed
- da05eb51debd 12.0 landed