similar to: problems building on solaris 2.6

Displaying 20 results from an estimated 7000 matches similar to: "problems building on solaris 2.6"

2000 Jan 18
1
Error when compiling for Solaris7
I cannot make openssh on Solaris. The 'make' fails on the first file. Here are the commands and the output. Essentially, I pre-built EGD, SSL, and ran: configure make make errors are listed at the bottom. Can anyone help me get this compiled on Solaris7? Steve sdn at sprintlabs.com ./configure --prefix=/common --sysconfdir=/etc/ssh --with-egd-pool=/common/bin/egd.pl loading cache
2001 Oct 30
1
[PATCH] for solaris 2.6
I didn't see this one applied to the repository yet. It may not be the best patch possible... basic problem is that _LARGEFILE64_SOURCE needs to be defined on Solaris 2.6 if AC_SYS_LARGEFILE ends up doing a '#define _FILE_OFFSET_BITS 64' If _FILE_OFFSET_BITS == 64, then <sys/resource.h> will define a 'struct rlimit64' but NOT define a 'struct rlimit' leading to
2001 May 15
0
openssh 2.9p1 on Solaris 2.6 with AFS
hello, I'm attempting to compile 2.9p1 on Solaris 2.6 with AFS support. I am not using Kerberos aside from AFS. The installation notes state that Kerberos IV is required by AFS. Since the Kerberos libraries and header files do not appear to be distributed with AFS, I downloaded and installed ftp://ftp.pdc.kth.se/pub/krb/src/krb4-1.0.8.tar.gz ./configure --sysconfdir=/etc/ssh
2001 Jul 11
0
Solaris 2.6: Undefined symbol seed_rng
Hi, I hope I'm not asking some FAQ, but I can't compile openssh-2.9p2 on maas34:openssh-2.9p2 {173} uname -a SunOS maas34 5.6 Generic_105181-23 sun4u sparc SUNW,Ultra-5_10 using: maas34:openssh-2.9p2 {174} gcc -v Reading specs from /opt/local/gcc-2.95.2/lib/gcc-lib/sparc-sun-solaris2.6/2.95.2/specs gcc version 2.95.2 19991024 (release) I get: maas34:openssh-2.9p2 {172}
2000 Jun 13
2
2.2.1p1 / AIX 4.2.1.0.06 login nits
Hi. New (2.1.1p1) login code is nicer on AIX (4.2.1.0.06). Thanks. A couple of issues, though, which I haven't really dug into yet. I'm wondering if anyone else has seen them? If not, I'll investigate & report. 1. If I set "UseLogin" to "yes", everything seems fine except that the authentication agent forwarding doesn't work. The "SSH"
2000 May 26
4
openssh-2.1.0p2 ans Solaris 8
I have some troubles with subj and proper utmpx/wtmpx functionality. After successfull ssh connect to Solaris 8 box, I run #w 11:59am up 13:45, 1 user, load average: 0.00, 0.01, 0.02 User tty login@ idle JCPU PCPU what root console 11:43am 9 bash # Record about my pts/1 login is absent. Next command I run from Solaris 8 console
2001 Apr 10
2
Compiling openssh 2.5.p1 on unixware 7.0.1
Hi. I'm tryng to compile openssh 2.5.p1 (latest) on sco unixware 7.0.1 and I'm getting this error in make: cc -o sshd sshd.o auth.o auth1.o auth2.o auth-chall.o auth2-chall.o auth-rhosts.o auth-options.o auth-krb4.o auth-pam.o auth2-pam.o auth-passwd.o auth-rsa.o auth-rh-rsa.o auth-sia.o dh.o sshpty.o log-server.o sshlogin.o loginrec.o servconf.o serverloop.o md5crypt.o session.o
2000 Aug 26
0
New chroot patch, for 2.1.1p4
Hi there, everybody; As promised, here's the new version for my chroot patch. It applies cleanly over OpenSSH 2.1.1p4, and I'm attaching 2 versions: - openssh-2.1.1p4-chroot.patch-wc, is the chroot patch plus a "--with-chroot" patch for the "configure" script. - openssh-2.1.1p4-chroot.patch, is the same without the "--with-chroot" part. Have fun,
2000 Oct 04
0
2.2.0p1 chroot patch
Hi there, everyone; Attached to this mail is the 2.2.0p1 version of my chroot patch. For those of you interested, my usual warning: This is NOT plug&pray. You'll have to build a whole binaries/libs/conf files tree within the new root. (it's just like the "classic" anonymous ftp behaviour) Configure with "configure --with-chroot" to use. Regards; RC --
2000 Jun 14
1
OpenSSH 2.1.1p1 on SCO Unixware 7.1.0
Yo All! I was just trying out OpenSSH 2.1.1p1 on SCO Unixware 7.1.0. The "configure" dies. See below. This seems to be the problem: if test -d "$f" -o -e "$f" ; then conf_lastlog_location=$f fi test is expecting a "shell option" after the "-o". If I run "/bin/sh ./configure" it fails. If I run "/bin/bash ./configure it
2000 Jan 17
5
AANOUNCE: openssh-1.2.1pre27
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A couple of silly errors, and one dangerous bug were in the pre26 release. This release corrects them. http://violet.ibs.com.au/openssh/files/openssh-1.2.1pre27.tar.gz If you want RPMs or any of the other files, please use a mirror: http://violet.ibs.com.au/openssh/files/MIRRORS.html Changes: - Using __snprintf is *NOT SAFE* on old Solaris.
2000 Jan 17
5
AANOUNCE: openssh-1.2.1pre27
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A couple of silly errors, and one dangerous bug were in the pre26 release. This release corrects them. http://violet.ibs.com.au/openssh/files/openssh-1.2.1pre27.tar.gz If you want RPMs or any of the other files, please use a mirror: http://violet.ibs.com.au/openssh/files/MIRRORS.html Changes: - Using __snprintf is *NOT SAFE* on old Solaris.
2009 Dec 25
2
[openssh-portable] utmpx and ut_name
Hello OpenSSH hackers, The last couple of weeks I've been figuring out how hard it is to replace FreeBSD's <utmp.h> with <utmpx.h>. I don't think utmpx is perfect, but at least it's better than what we have now and at least it has gone through some form of standardisation. I noticed POSIX says the following [1]: | The <utmpx.h> header shall define the utmpx
1999 Dec 20
2
Portability hacks + alpha HPUX1020 port
Hi, Attached is a patch to 1.2.1pre18 that includes a number of portability changes, and more a more complete HPUX10.20 implementation. Thanks to Ben Taylor's utmpx patch, utmpx and wtmpx support are now in for HP, with a few caveats. It compiles cleanly on HPUX10.20 with gcc, cleanly on Linux, and with a few minor warnings on Solaris 2.6. Most compat changes are made via autoconf which
2011 Sep 02
1
problems building openssh-5.8p1 on qnx
I am having trouble figuring out how to build openssh-5.8p1 for QNX 6.5. I am trying to build on linux, cross-compiling for armv7. If I configure like this: configure CC=ntoarmv7-gcc --host=i686-pc-linux-gnu --target=arm-unknown-nto-qnx6.5.0 then I get these errors: sshconnect.o: In function `timeout_connect': sshconnect.c:(.text+0x778): undefined reference to
1998 May 11
1
(wtmp) Suggestion to samba
Joao Carlos Mendes Luis <jonny@coe.ufrj.br> wrote: > I think it would be useful if samba had a utmp log interface. > I know that it's possible to see who is logged with smbstatus, but > sometimes a simple who(1) or w(1) is more efficient and ubiquitous. If you were to search for 'wtmp' in the 1997 archives (via the Samba web pages), you would find one interesting
1999 Dec 27
2
Suggestion: login.c->record_login()
Hi, A lot of the problems with openssh portability so far appear to be with the login record functionality, i.e. lastlog support, and variations on handling utmp vs. utmpx etc. Looking at for-profit SSH 1.2.27, login.c is rather embarassing spaghetti code, so laden with '#ifdef's it's almost impossible to read. OpenSSH's code isn't anything like that, but then it doesn't
2002 Jul 23
2
Irix UseLogin wtmp/utmp bug
I am using the "UseLogin yes" configuration parameter to call the /usr/bin/login program on SGI Irix, (we are using Irix version 6.5.13). I do this because the SGI login program is AFS awhere and checks out a token for you and I do not want to compile the Kerberos version of sshd, (it is to messy for me to support). Everything seems to work fine accept the wtmp(x) and utmp(x) files do
2000 Jul 03
0
FreeBSD 3.5-STABLE
gcc -g -O2 -Wall -I/usr/local/ssl/include -DETCDIR=\"/usr/local/etc\" -DSSH_PROGRAM=\"/usr/local/bin/ssh\" -DSSH_ASKPASS_DEFAULT=\"/usr/local/libexec/ssh/ssh-askpass\" -DHAVE_CONFIG_H -c loginrec.c loginrec.c: In function `construct_utmp': loginrec.c:619: structure has no member named `ut_user' loginrec.c:619: structure has no member named `ut_user'
2000 Jul 01
0
Problem with cleaning utmp entry
Hello I have problem with OpenSSH 2.1.1p1 on libc5 system (Slackware 4). I'm not sure if I had those problems with 1.2.x version of OpenSSH (on the same system), but I don't think so. When someone ends ssh session (logout, or something) utmp entry for that user doesn't get erased from UTMP file. In 'finger' I can see a lot of multiplicied users that are not actually logged