[Bug 2315] New: OpenSSH 6.7p1 on AIX 7.1 compile issue

bugzilla-daemon at mindrot.org bugzilla-daemon at mindrot.org
Sat Nov 15 08:26:36 EST 2014


            Bug ID: 2315
           Summary: OpenSSH 6.7p1 on AIX 7.1 compile issue
           Product: Portable OpenSSH
           Version: 6.7p1
          Hardware: PPC
                OS: AIX
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Build system
          Assignee: unassigned-bugs at mindrot.org
          Reporter: yaberger at ca.ibm.com


I'm trying to compile OpenSSH 6.7p1 on AIX 7.1 TL2 SP3 with IBM XL
C/C++, OpenSSL 1.0.1j and zlib 1.2.8
This is my compile procedure:
export PATH=$PATH:/usr/vac/bin
/usr/bin/gzip -cd openssh-6.7p1.tar.gz |/usr/bin/tar xf -
cd openssh-6.7p1
./configure --prefix=/usr/local/openssh-6.7p1 --sysconfdir=/etc/ssh
--without-shadow --with-ssl-dir=/usr/local/openssl

And I get the following error:
cc -qlanglvl=extc89 -o ssh ssh.o readconf.o clientloop.o sshtty.o 
sshconnect.o sshconnect1.o sshconnect2.o mux.o  roaming_common.o
roaming_client.o -L. -Lopenbsd-compat/ -L/usr/local/openssl/lib
-L/usr/local/zlib/lib  -blibpath:/usr/lib:/lib -lssh -lopenbsd-compat 
-lcrypto -lz  
ld: 0711-317 ERROR: Undefined symbol: .va_copy
ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more
make: 1254-004 The error code from the last command is 8.

Same error on AIX 5.3 TL12 SP9 with IBM XL C/C++ and AIX 6.1
TL8 SP3 with IBM XL C/C++
I was able to compile OpenSSH 6.6p1 with OpenSSL 1.0.1i and zlib 1.2.8
with this procedure without issue.

I've found that by adding this in sshbuf-getput-basic.c and by
replacing every occurence of va_copy by VA_COPY, I'm now able to
compile it.
#ifndef VA_COPY
# ifdef HAVE_VA_COPY
#  define VA_COPY(dest, src) va_copy(dest, src)
# else
#  ifdef HAVE___VA_COPY
#   define VA_COPY(dest, src) __va_copy(dest, src)
#  else
#   define VA_COPY(dest, src) (dest) = (src)
#  endif
# endif

This fix/workaround is inspired by openbsd-compat/bsd-snprintf.c
Do you believe it would be the right fix to apply?
If so, could it be done in master so that next release include it?
If it's not the right fix, anyone willing to look at this issue and
suggest another fix?

Best regards,

Yannick Bergeron

You are receiving this mail because:
You are watching the assignee of the bug.

More information about the openssh-bugs mailing list