I was facing the same error when using active state perl for compiling postgres with meson on windows. I used active state perl because it was working fine for pg compilations until pg-16.
On 2023-12-07 14:16:52 -0500, Dave Cramer wrote: > On Thu, 7 Dec 2023 at 13:53, Andres Freund <andres@anarazel.de> wrote: > > > Hi, > > > > On 2023-12-07 12:54:27 -0500, Dave Cramer wrote: > > > state-exec: run failed: cannot create new executor meta: cannot get > > > matching bin by path: no matching binary by path > > > > > "C:\\Users\\Administrator\\AppData\\Local\\activestate\\cache\\b9117b06\\exec\\perl.EXE" > > > state-exec: Not user serviceable; Please contact support for assistance. > > > > > > anyone seen this or have a fix ? > >
I am facing the same issue while compiling the pg17. I have resolved this issue by installing perl from "https://strawberryperl.com/". In addition to installing the strawberry's perl, I had to adjust the environment variable PATH values. That is, I had to give higher priority to strawberry's perl bin paths.
(Please note that I haven't removed activestate's perl, or mingw's perl. So whenever, I will need to build pg16 or lower, I have to readjust activestate's perl bin path in the environment variable.)
> > I've not seen that before. Please provide a bit more detail. Compiler, > > building with ninja or msbuild/visual studio, when exactly you're > > encountering > > the issue, ... > > > > Windows Server 2019 > VS 2019 > building with ninja
I don't think this is sufficient detail to provide you with advice / fix problems / whatnot. Please provide complete logs of configuring and building.