3.18.x deps 2023 08 28 16 39 01 610533

[larsewi]

• Updated lmdb from 0.9.30 to 0.9.31
• Updated zlib from 1.2.13 to 1.3
• Updated openssl from 1.1.1t to 1.1.1v
• Updated libxml2 from 2.11.2 to 2.11.5
• Updated diffutils from 3.9 to 3.10
• Updated openldap from 2.6.4 to 2.6.6
• Updated libcurl-hub from 8.0.1 to 8.2.1
• Updated git from 2.40.1 to 2.42.0
• Updated postgresql from 13.10 to 13.12
• Updated php from 8.0.28 to 8.0.30
• Updated libcurl from 8.0.1 to 8.2.1

[larsewi]

@cf-bottom build with exotics plz

[cf-bottom]

Alright, I triggered a build:

(with exotics)

Jenkins: https://ci.cfengine.com/job/pr-pipeline/9695/

Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-9695/

[Lex-2008]

looks goold! Now let's see if it builds.

[craigcomstock]

retrying aix builds with reverted aix64 commit, worked two ways manually for me on aix71 so let's see if the job works

[craigcomstock]

not sure why aix71 is failing or using the odd IBM compiler

16:38:05 /opt/IBM/xlc/13.1.3/bin/.orig/cc: 1501-210 (W) command option -O contains an incorrect subargument
16:38:05 ld: 0706-005 Cannot find or open file: no-omit-frame-pointer
16:38:05        ld:fopen(): A file or directory in the path name does not exist.
16:38:05 gmake[1]: Leaving directory '/home/jenkins/workspace/testing-pr/label/PACKAGES_ppc64_aix_71/openssl/BUILD/openssl-1.1.1v'
16:38:05 gmake[1]: *** [Makefile:741: libcrypto.a] Error 255
16:38:05 gmake: *** [Makefile:174: all] Error 2
16:38:05 
16:38:05 
16:38:05 RPM build errors:

and if I even just try running that cc I get

bash-5.1$ /opt/IBM/xlc/13.1.3/bin/.orig/cc
/opt/IBM/xlc/13.1.3/bin/.orig/cc: 1501-287 (S) This compiler does not support AIX 7.1. Please check with IBM (http://www-01.ibm.com/support/docview.wss?rs=43&uid=swg21326972) to see if there is a PTF for this compiler that supports this AIX level.

It should be using /usr/bin/gcc which is /opt/freeware/bin/gcc which is /opt/freeware/bin/gcc-10 (which maybe should be gcc-6 according to setup guidelines we have).

[Lex-2008]

regarding aix7 - I believe issue is that it chooses aix-cc target, while it should be aix-gcc.

console output for a recent build has this line:

Configuring OpenSSL version 1.1.1v (0x1010116fL) for aix-cc

while in our buildscripts we have this patch file (although on master branch), which adds aix7-gcc profile, based on (presumably, existing) aix-gcc one.

Changes in OpenSSL between versions 1.1.1t and 1.1.1v don't show something relevant, sadly.

We can check if it's caused by change in our infrastructure or by changing OpenSSL versions by renaming/moving all compiled OpenSSL packages from build-artifacts-cache and requesting a build of a "vanilla" 3.18.x (with old OpenSSL version) - if it fails, the problem is caused by our infra change.

Or, we can read through their configure script and see how it detects gcc

[craigcomstock]

aix71 retry after fixing that build host configuration/software a bit

[craigcomstock]

retry aix71 after making the change that worked for me manually/locally on aix71 build host

[craigcomstock]

@cf-bottom jenkins with exotics please

[cf-bottom]

Sure, I triggered a build:

(with exotics)

Jenkins: https://ci.cfengine.com/job/pr-pipeline/9806/

Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-9806/

[craigcomstock]

checking rhel7 and aix*, will squash commits when "done"

[craigcomstock]

bad shell code in spec file for openssl, retry:

[craigcomstock]

@larsewi the CI builds look good, rhel7 🟢 aix5 and aix7 are in progress testing so past the building of openssl that was holding us up.

I squashed the openssl build spec commits into one.

@cf-bottom jenkins please with exotics

[cf-bottom]

Alright, I triggered a build:

(with exotics)

Jenkins: https://ci.cfengine.com/job/pr-pipeline/9828/

Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-9828/

[craigcomstock]

bad shell code in spec file for openssl, retry:

That build is successful in terms of rhel7, aix5 and aix7 all passing their testing-pr jobs. So @larsewi I think we are nearly ready to go with this PR.

[larsewi]

@craigcomstock I think we can merge this. Don't you?