openssh 4.6p1 bug / IRIX

Darren Tucker dtucker at
Fri Mar 23 16:39:54 EST 2007

g.fischer at wrote:
> hello,
> little problem compiling openssh 4.6p1 on irix using mipspro 7.4.x.
> c99 -o sshd sshd.o auth-rhosts.o auth-passwd.o auth-rsa.o auth-rh-rsa.o 
> sshpty.o sshlogin.o servconf.o serverloop.o auth.o auth1.o auth2.o 
> auth-options.o session.o auth-chall.o auth2-chall.o groupaccess.o 
> auth-skey.o auth-bsdauth.o auth2-hostbased.o auth2-kbdint.o auth2-none.o 
> auth2-passwd.o auth2-pubkey.o monitor_mm.o monitor.o monitor_wrap.o 
> kexdhs.o kexgexs.o auth-krb5.o auth2-gss.o gss-serv.o gss-serv-krb5.o 
> loginrec.o auth-pam.o auth-shadow.o auth-sia.o md5crypt.o audit.o 
> audit-bsm.o platform.o -L. -Lopenbsd-compat/ -L/usr/local/lib 
> -L/usr/local2/lib -L/usr/nekoware/lib -L/usr/freeware/lib32 -lssh 
> -lopenbsd-compat     -liaf -lcrypto -lz  -lgen
> ld32: ERROR   33 : Unresolved text symbol "set_id" -- 1st referenced by 
> session.o.

set_id is inside "HAVE_LIBIAF" which I believe is specific to SCO. (?) 
   Maybe IRIX has something similar (or similarly named).

Defining BROKEN_LIBIAF at build time (eg "./configure 
--with-cflags=-DBROKEN_LIBIAF") will probably get your build going.

Looking at it, I think that configure should probably check for set_id 
explicitly and session.c should use HAVE_SET_ID in addition to HAVE_LIBAIF.

Darren Tucker (dtucker at
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
     Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.

More information about the openssh-unix-dev mailing list