Ticket #135 (closed defect)
Opened 2 years ago
Last modified 2 years ago
libssh2 1.2.3 compile failure under solaris 8
| Reported by: | anonymous | Owned by: | bagder |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | misc | Version: | |
| Keywords: | Cc: | bagder | |
| Blocked By: | Blocks: |
Description
libssh2 1.2.3 no longer compiles cleanly on one of my solaris 8 hosts. version 1.2.2 compiles without complaint.
host:/tmp > gtar -zxpf libssh2-1.2.3.tar.gz
host:/tmp > cd libssh2-1.2.3
host:/tmp/libssh2-1.2.3 > ./configure --with-libssl-prefix=/usr/local/openssl >& /dev/null && echo $status
0
host:/tmp/libssh2-1.2.3 > gmake >& /dev/null ; echo $status
2
host:/tmp/libssh2-1.2.3 > gmake
Making all in src
gmake[1]: Entering directory `/tmp/libssh2-1.2.3/src'
gmake all-am
gmake[2]: Entering directory `/tmp/libssh2-1.2.3/src'
source='agent.c' object='agent.lo' libtool=yes \
DEPDIR=.deps depmode=gcc /bin/bash ../depcomp \
/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I../include -I../src -I/usr/local/openssl/include -I/usr/local/include -g -O2 -c -o agent.lo agent.c
libtool: compile: gcc -DHAVE_CONFIG_H -I../include -I../src -I/usr/local/openssl/include -I/usr/local/include -g -O2 -c agent.c -Wp,-MD,.deps/agent.TPlo -fPIC -DPIC -o .libs/agent.o
agent.c: In function `agent_connect_unix':
agent.c:145: parse error before `1'
agent.c:157: request for member `sun_family' in something not a structure or union
agent.c:158: request for member `sun_path' in something not a structure or union
agent.c:158: request for member `sun_path' in something not a structure or union
agent.c:159: invalid lvalue in unary `&'
gmake[2]: * [agent.lo] Error 1
gmake[2]: Leaving directory `/tmp/libssh2-1.2.3/src'
gmake[1]: * [all] Error 2
gmake[1]: Leaving directory `/tmp/libssh2-1.2.3/src'
gmake: * [all-recursive] Error 1
host:/tmp/libssh2-1.2.3 >
Change History
comment:1 Changed 2 years ago by bagder
comment:2 Changed 2 years ago by bagder
This is already fixed!

Can you please the current git or tomorrow's daily snapshot and see if the bug is still there? There have been fixes applied that might've corrected the problem.