On Thu, 20 Feb 2020 at 03:51, Val Baranov <val.baranov at duke.edu> wrote:> On Tuesday, February 18, 2020 8:31 PM Darren Tucker wrote:[...]> Daren, This is definitely ver. 8.2 - my apologies, but the output provided from session > where " libressl-api-compat.c " was substituted with the older version in attempts to find > out if this may have any difference.What options did you give to configure? In your mail prior to the release you had --without-openssl-header-check, which makes me suspect you have mismatched openssl headers somewhere on your system which could potentially cause this.> So, what you may recommend? Switch over to gcc/gmake? This will leave AIX native > compiler forever out of scope. As an option and if needed, I may perform debugging per > your directions (if possible).Well I'd like to see it work, but at the moment it's not clear to me what the problem is. -- Darren Tucker (dtucker at dtucker.net) GPG key 11EAA6FA / A86E 3E07 5B19 5880 E860 37F4 9357 ECEF 11EA A6FA (new) Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.
On Thu, 20 Feb 2020 at 10:48, Darren Tucker <dtucker at dtucker.net> wrote:> Well I'd like to see it work, but at the moment it's not clear to me > what the problem is.Turned out I saved an old VAC (8.0) eval kit for my olde faithful AIX box, so I was able to build OpenSSH 8.2 with VAC against OpenSSL 1.1.1d thusly: $ blibpath=/usr/lib:/usr/local/lib CC=/usr/vac/bin/cc ./configure --with-ssl-dir=/usr/local --with-zlib=/usr/local && make [...] $ ./ssh -V OpenSSH_8.2p1, OpenSSL 1.1.1d 10 Sep 2019 Could you please send me the exact configure invocation you used and the Makefile and config.h that it created? I'd also suggest you search your system for "openssl" directories containing header files and temporarily rename the ones you do not intend to use before running OpenSSH's configure (without disabling the openssl header check) to make sure it's finding the one you intend to use. Thanks. -- Darren Tucker (dtucker at dtucker.net) GPG key 11EAA6FA / A86E 3E07 5B19 5880 E860 37F4 9357 ECEF 11EA A6FA (new) Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.
FYI. I just completed building it on my AIX 5.3 system - and using xlc v11. As I mentioned in my earlier email use CC=xlc and these issues go away. To see what is changed examine the contents of the file appropriate for your system level: root at x064:[/data/prj/openbsd/openssh/openssh-8.2p1]ls -l /etc/vac* -rw-r--r--??? 1 bin????? bin?????????? 37731 Aug 02 2018? /etc/vac.cfg.53 -rw-r--r--??? 1 bin????? bin?????????? 39672 Aug 02 2018? /etc/vac.cfg.61 -rw-r--r--??? 1 bin????? bin?????????? 39681 Aug 02 2018? /etc/vac.cfg.71 -rw-r--r--??? 1 bin????? bin?????????? 39611 Aug 02 2018? /etc/vac.cfg.72 On 2/20/2020 12:36 PM, Darren Tucker wrote:> On Thu, 20 Feb 2020 at 10:48, Darren Tucker <dtucker at dtucker.net> wrote: >> Well I'd like to see it work, but at the moment it's not clear to me >> what the problem is. > Turned out I saved an old VAC (8.0) eval kit for my olde faithful AIX > box, so I was able to build OpenSSH 8.2 with VAC against OpenSSL > 1.1.1d thusly: > > $ blibpath=/usr/lib:/usr/local/lib CC=/usr/vac/bin/cc ./configure > --with-ssl-dir=/usr/local --with-zlib=/usr/local && make > [...] > $ ./ssh -V > OpenSSH_8.2p1, OpenSSL 1.1.1d 10 Sep 2019 > > Could you please send me the exact configure invocation you used and > the Makefile and config.h that it created? > > I'd also suggest you search your system for "openssl" directories > containing header files and temporarily rename the ones you do not > intend to use before running OpenSSH's configure (without disabling > the openssl header check) to make sure it's finding the one you intend > to use. > > Thanks. >