- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- libssh2 gmake failure
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-30-2009 12:10 PM
тАО12-30-2009 12:10 PM
getting error when doing a gmake check:
Contacted the developer but that process is pretty slow!
PASS: simple
Fingerprint: A0 90 21 52 25 7A 06 7F B9 7B 52 CE FA A6 93 7F
Authentication methods: publickey,password,keyboard-interactive
Authentication by public key failed!
FAIL: ssh2.sh
====================================================
1 of 2 tests failed
Please report to libssh2-devel@lists.sourceforge.net
====================================================
gmake[2]: *** [check-TESTS] Error 1
gmake[2]: Leaving directory `/var/tmp/Cary/libssh2-1.2.2/tests'
gmake[1]: *** [check-am] Error 2
gmake[1]: Leaving directory `/var/tmp/Cary/libssh2-1.2.2/tests'
gmake: *** [check-recursive] Error 1
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-30-2009 12:55 PM
тАО12-30-2009 12:55 PM
Re: libssh2 gmake failure
The ssh binaries provided by depot from the web site http://software.hp.com work well. Are you compiling for a specific feature?
https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=T1471AA
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2010 04:23 AM
тАО01-07-2010 04:23 AM
Re: libssh2 gmake failure
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2010 04:41 AM
тАО01-07-2010 04:41 AM
Re: libssh2 gmake failure
Do you have all runtime dependencies installed?
http://hpux.connect.org.uk/hppd/hpux/Networking/WWW/curl-7.19.6/
Regards,
Robert-Jan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2010 05:19 AM
тАО01-07-2010 05:19 AM
Re: libssh2 gmake failure
db gettext heimdal libiconv libidn openldap openssl termcap zlib
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2010 08:43 AM
тАО01-07-2010 08:43 AM
Re: libssh2 gmake failure
Which libssh2 kit? On what? Using which
compiler? "configure"d and built how?
"uname -a"? Any useful info at all?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2010 08:59 AM
тАО01-07-2010 08:59 AM
Re: libssh2 gmake failure
Tried libssh2-0.15 and 2-1.2.2
On what? Using which
compiler? "configure"d
I'm assuming gcc i do a ./configure
and built how? i do a gmake then a gmake check
the gmake check is what spits out the error.
tried make but that doesn't work i get:
# make
Make: Must be a separator on rules line 742. Stop.
"uname -a"?
HP-UX uhpc B.11.31 U ia64
Any useful info at all?
attached all results from configure,gmake and gmake check
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2010 02:47 PM
тАО01-07-2010 02:47 PM
Re: libssh2 gmake failure
no highly satisfactory results. On my HP-UX
(IA64 and PA-RISC) systems, the build seemed
to work, but I also got the "FAIL: ssh2.sh"
complaint. On my Solaris system, the build
failed (miserably). On my Tru64 system, the
build seemed to work, but the tests/ssh2.sh
script assumes many things about
/usr/sbin/sshd which aren't true there, so it
fails sooner there than on HP-UX.
Thus, to me, it doesn't seem to be highly
portable code, and that test isn't much
better (providing only a pass-fail status,
with no diagnostic info), so I'd either
complain to the maintainer, or ignore the
test and pretend that the code really works,
or else, if possible, try to find some better
code somewhere else.
Or dig in and do some serious debugging.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2010 10:01 PM
тАО01-07-2010 10:01 PM
SolutionOr, wait for me to get lucky...
Inspection of the failing test script reveals
that it's trying to run "/usr/sbin/sshd" (or
whatever SSHD is set to), listening on an
odd-ball port (4711), with a bunch of other
special-case options, and then it runs its
own "tests/ssh2" program, which tries to talk
to this instance of the "sshd" server.
Unfortunately, the "tests/ssh2" program (see
"tests/ssh2.c") expects, by default, to send
the user name "username", and if this is not
a valid user on your system, then the server
spits up. Running it in a diagnostic mode
("-d -e"), and then running "tests/ssh2"
manually:
[...]
Invalid user username from 127.0.0.1
debug1: audit event euid 0 user (unknown user) event 9 (INVALID_USER)
debug1: aud_sav_flag=1
input_userauth_request: invalid user username
debug1: audit event euid 0 user (invalid user) event 9 (INVALID_USER)
debug1: aud_sav_flag=1
debug1: PAM: initializing for "username"
debug1: PAM: setting PAM_RHOST to "localhost"
Failed none for invalid user username from 127.0.0.1 port 52157 ssh2
debug1: audit event euid 0 user (invalid user) event 3 (AUTH_FAIL_NONE)
debug1: userauth-request for user username service ssh-connection method publickey
debug1: attempt 1 failures 0
Failed publickey for invalid user username from 127.0.0.1 port 52157 ssh2
debug1: Entering record_failed_login uid 0
debug1: audit event euid 0 user (invalid user) event 6 (AUTH_FAIL_PUBKEY)
debug1: aud_sav_flag=1
Received disconnect from 127.0.0.1: 11: Normal Shutdown
debug1: do_cleanup
debug1: PAM: cleanup
debug1: audit event euid 0 user (invalid user) event 12 (CONNECTION_ABANDON)
debug1: aud_sav_flag=1
Without these debug options, the diagnostics
tend to go to the system log file
("/var/adm/syslog/syslog.log"), where you may
find the spoor of the previous test failures.
Luckily, the "tests/ssh2" program looks at
its environment, and if the environment
variable "USER" is defined, then its value is
used instead of "username". So, define
"USER" as some valid user name, and things
may improve.
As before:
dyi # gmake check
Making check in src
gmake[1]: Entering directory `/usr/local/src/libssh2/libssh2-1.2.2/src'
gmake[1]: Nothing to be done for `check'.
gmake[1]: Leaving directory `/usr/local/src/libssh2/libssh2-1.2.2/src'
Making check in example
gmake[1]: Entering directory `/usr/local/src/libssh2/libssh2-1.2.2/example'
Making check in simple
gmake[2]: Entering directory `/usr/local/src/libssh2/libssh2-1.2.2/example/simple'
gmake[2]: Nothing to be done for `check'.
gmake[2]: Leaving directory `/usr/local/src/libssh2/libssh2-1.2.2/example/simple'
gmake[2]: Entering directory `/usr/local/src/libssh2/libssh2-1.2.2/example'
gmake[2]: Nothing to be done for `check-am'.
gmake[2]: Leaving directory `/usr/local/src/libssh2/libssh2-1.2.2/example'
gmake[1]: Leaving directory `/usr/local/src/libssh2/libssh2-1.2.2/example'
Making check in tests
gmake[1]: Entering directory `/usr/local/src/libssh2/libssh2-1.2.2/tests'
gmake simple
gmake[2]: Entering directory `/usr/local/src/libssh2/libssh2-1.2.2/tests'
gmake[2]: `simple' is up to date.
gmake[2]: Leaving directory `/usr/local/src/libssh2/libssh2-1.2.2/tests'
gmake check-TESTS
gmake[2]: Entering directory `/usr/local/src/libssh2/libssh2-1.2.2/tests'
PASS: simple
Fingerprint: A0 90 21 52 25 7A 06 7F B9 7B 52 CE FA A6 93 7F
Authentication methods: publickey,password,keyboard-interactive
Authentication by public key failed!
FAIL: ssh2.sh
====================================================
1 of 2 tests failed
Please report to libssh2-devel@lists.sourceforge.net
====================================================
gmake[2]: *** [check-TESTS] Error 1
gmake[2]: Leaving directory `/usr/local/src/libssh2/libssh2-1.2.2/tests'
gmake[1]: *** [check-am] Error 2
gmake[1]: Leaving directory `/usr/local/src/libssh2/libssh2-1.2.2/tests'
gmake: *** [check-recursive] Error 1
Again, but defining "USER" ("sms" is valid
here):
dyi # USER=sms gmake check
Making check in src
gmake[1]: Entering directory `/usr/local/src/libssh2/libssh2-1.2.2/src'
gmake[1]: Nothing to be done for `check'.
gmake[1]: Leaving directory `/usr/local/src/libssh2/libssh2-1.2.2/src'
Making check in example
gmake[1]: Entering directory `/usr/local/src/libssh2/libssh2-1.2.2/example'
Making check in simple
gmake[2]: Entering directory `/usr/local/src/libssh2/libssh2-1.2.2/example/simple'
gmake[2]: Nothing to be done for `check'.
gmake[2]: Leaving directory `/usr/local/src/libssh2/libssh2-1.2.2/example/simple'
gmake[2]: Entering directory `/usr/local/src/libssh2/libssh2-1.2.2/example'
gmake[2]: Nothing to be done for `check-am'.
gmake[2]: Leaving directory `/usr/local/src/libssh2/libssh2-1.2.2/example'
gmake[1]: Leaving directory `/usr/local/src/libssh2/libssh2-1.2.2/example'
Making check in tests
gmake[1]: Entering directory `/usr/local/src/libssh2/libssh2-1.2.2/tests'
gmake simple
gmake[2]: Entering directory `/usr/local/src/libssh2/libssh2-1.2.2/tests'
gmake[2]: `simple' is up to date.
gmake[2]: Leaving directory `/usr/local/src/libssh2/libssh2-1.2.2/tests'
gmake check-TESTS
gmake[2]: Entering directory `/usr/local/src/libssh2/libssh2-1.2.2/tests'
PASS: simple
Fingerprint: A0 90 21 52 25 7A 06 7F B9 7B 52 CE FA A6 93 7F
Authentication methods: publickey,password,keyboard-interactive
Authentication by public key succeeded.
PASS: ssh2.sh
==================
All 2 tests passed
==================
gmake[2]: Leaving directory `/usr/local/src/libssh2/libssh2-1.2.2/tests'
gmake[1]: Leaving directory `/usr/local/src/libssh2/libssh2-1.2.2/tests'
Making check in docs
gmake[1]: Entering directory `/usr/local/src/libssh2/libssh2-1.2.2/docs'
gmake[1]: Nothing to be done for `check'.
gmake[1]: Leaving directory `/usr/local/src/libssh2/libssh2-1.2.2/docs'
gmake[1]: Entering directory `/usr/local/src/libssh2/libssh2-1.2.2'
gmake[1]: Nothing to be done for `check-am'.
gmake[1]: Leaving directory `/usr/local/src/libssh2/libssh2-1.2.2'
This could all be documented somewhere, but I
didn't see it. Perhaps the sshd programs on
the developers' systems are less fussy than
this one, and don't care if the specified
user name is valid. (Or perhaps they all
have a user named "username".)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-08-2010 04:29 AM
тАО01-08-2010 04:29 AM