Re: ActiveState Perl is not valid anymore to build PG17 on the Windows 10/11 platforms, So Documentation still suggesting it should be updated

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Yasir <yasir(dot)hussain(dot)shah(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: ActiveState Perl is not valid anymore to build PG17 on the Windows 10/11 platforms, So Documentation still suggesting it should be updated
Date: 2024-07-16 12:23:11
Message-ID: c97a2ed0-c9c2-4c09-9ff6-6918e72e3015@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 2024-07-16 Tu 7:46 AM, Yasir wrote:
> Hi Hackers,
>
> Recently, I compiled PG17 on the windows. Till PG16 "ActiveState
> Perl", as instructed in the documentation
> <https://www.postgresql.org/docs/16/install-windows-full.html#INSTALL-WINDOWS-FULL-REQUIREMENTS>,
> was being used successfully on the Windows 10/11 to compile PG.
> However, it looks like that "ActiveState Perl" is not valid anymore to
> compile PG17 on Windows 10/11 but documentation
> <https://www.postgresql.org/docs/17/installation-platform-notes.html#WINDOWS-REQUIREMENTS> still
> suggests it. Therefore, I think documentation needs to be updated.
> Moreover, I had to install "strawberry's perl" in order to compile
> PG17 on Windows 10/11. Please check out the thread "errors building on
> windows using meson
> <https://www.postgresql.org/message-id/flat/CADK3HHLQ1MNmfXqEvQi36D_MQrheOZPcXv2H3s6otMbSmfwjzg%40mail.gmail.com>"
> highlighting the issue.
>

See https://postgr.es/m/4acddcd4-1c08-44e7-ba60-cab1022599e3@dunslane.net

I agree we should fix the docco.

cheers

andrew

--

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2024-07-16 12:28:09 Re: CI, macports, darwin version problems
Previous Message Noah Misch 2024-07-16 12:19:35 Re: Use read streams in CREATE DATABASE command when the strategy is wal_log