Re: buildfarm + meson - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: buildfarm + meson
Date
Msg-id 1af34448-b10e-ac65-ef5d-5febea003447@dunslane.net
Whole thread Raw
In response to Re: buildfarm + meson  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers


On 2023-03-18 Sa 21:32, Andrew Dunstan wrote:


On 2023-03-18 Sa 19:00, Andres Freund wrote:
Hi,

On 2023-03-18 17:53:38 -0400, Andrew Dunstan wrote:
On 2023-03-11 Sa 16:25, Andres Freund wrote:
Hi,

On 2023-03-09 18:31:10 -0500, Andrew Dunstan wrote:
Another thing: the test for uuid.h is too strict. On Fedora 36 the OSSP
header is in /usr/include, not /usr/include/ossp (I got around that for now
by symlinking it, but obviously that's a nasty hack we can't ask people to
do)
Yea, that was just wrong. It happened to work on debian and a few other OSs,
but ossp's .pc puts whatever the right directory is into the include
path. Pushed the fairly obvious fix.
Another issue: building plpython appears impossible on Windows because it's
finding meson's own python:


Program python3 found: YES (C:\Program Files\Meson\meson.exe runpython)
Could not find Python3 library 'C:\\Program
Files\\Meson\\libs\\python311.lib'
Any more details - windows CI builds with python. What python do you want to
use and where is it installed?


It's in c:/python37, which is at the front of the PATH. It fails as above if I add -Dplpython=enabled to the config.


Looks like the answer is not to install using the MSI installer, which provides its own Python, but to install meson and ninja into an existing python installation via pip. That's a bit sad, but manageable.


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Commitfest 2023-03 starting tomorrow!
Next
From: Melanie Plageman
Date:
Subject: Re: Should vacuum process config file reload more often