Hi Tom,
We have tested this patch on our environment, and we see all the basic tests are passing and Postgres binary is up.
ok 226 + eager_aggregate 921 ms
# parallel group (2 tests): oidjoins event_trigger
ok 227 + oidjoins 199 ms
ok 228 + event_trigger 255 ms
ok 229 - event_trigger_login 55 ms
ok 230 - fast_default 207 ms
ok 231 - tablespace 533 ms
1..231
# All 231 tests passed.
We have set the below flags for building the source
export OBJECT_MODE=64
export FLAG64="-maix64"
export CC__=/opt/freeware/bin//gcc-12
export CXX__=/opt/freeware/bin//g++-12
export CC64="${CC__}"
export CFLAGS="${FLAG64} -O2 "
export GLOBAL_CC_OPTIONS="-O2"
export CC="${CC64} "
export LDFLAGS="-L/opt/freeware/lib64 -L/usr/lib64 -L/opt/freeware/lib -L/usr/lib -Wl,-blibpath:/opt/freeware/lib64:/opt/freeware/lib:/usr/lib:/lib"
export LDFLAGS=$LDFLAGS:/opt/freeware/lib64/perl5/5.38/CORE/:
export PYTHON=/opt/freeware/bin/python3.9
export AR='/usr/bin/ar -X64’
The patch is build on top of this commit, which is older
commit c581c9a7ac2af2c75567013f25125bd294d49ff2
We are trying to integrate the changes to the latest HEAD
I would like to know if there are any specific environment variables are set on your build machine.
