Thanks Andrew.
The build's still running but the CPPFLAGS hint does seem to have helped (see below).
Unless advised otherwise, I intend to let that option be, so as to get bichir back online. If a future commit 'fixes' things, I could rollback this flag to test things out (or try out other options if required).
On Wed, 7 Apr 2021 at 21:49, Andrew Dunstan <andrew@dunslane.net> wrote:
> On 4/7/21 2:16 AM, Thomas Munro wrote:
> > On Wed, Apr 7, 2021 at 5:44 PM Robins Tharakan <tharakan@gmail.com> wrote:
> >> Bichir's been stuck for the past month and is unable to run regression tests since 6a2a70a02018d6362f9841cc2f499cc45405e86b.
> > ...If it is indeed
> > something like that and not a bug in my code, then I was thinking that
> > the main tool available to deal with it would be to set WAIT_USE_POLL
> > in the relevant template file, so that we don't use the combination of
> > epoll + signalfd on illlumos, but then WSL1 thows a spanner in the
> > works because AFAIK it's masquerading as Ubuntu, running PostgreSQL
> > from an Ubuntu package with a freaky kernel. Hmm.
> To test this the OP could just add
> CPPFLAGS => '-DWAIT_USE_POLL',
> to his animal's config's config_env stanza.
This did help in getting past the previous hurdle.
postgres@WSLv1:/opt/postgres/bf/v11/buildroot/HEAD/bichir.lastrun-logs$ grep CPPFLAGS configure.log| grep using
configure: using CPPFLAGS=-DWAIT_USE_POLL -D_GNU_SOURCE -I/usr/include/libxml2
configure:19511: using CPPFLAGS=-DWAIT_USE_POLL -D_GNU_SOURCE -I/usr/include/libxml2
postgres@WSLv1:/opt/postgres/bf/v11/buildroot/HEAD/bichir.lastrun-logs$ grep -A2 "creating database" lastcommand.log
============== creating database "regression" ==============
CREATE DATABASE
ALTER DATABASE
-
thanks
robins
