I've messed so much with various things that I've ended up completely
wiping out the src tree several times and trying again. strange that it
just worked for you. I'm using the 7.3.1.1m C compiler on a Origin 2000
Irix 6.5.10m... would it help do you think to install autoconf and
automake etc? or is that a non-issue? I'm also a little confused as to
whether to use the n32 or 64 ABI? We've got a bunch of different SGI's
here ranging from 02's to the Origin 2000's would it help to try using
maybe a 32 bit architecture SGI?
I've traced down the libs and they are in their respective paths and look
ok. I've tried modifying the ar and linker command lines. I've tried
various CFLAGS, but I keep getting exactly the same problem... :-)
Thanks for all the help! I'm learning a lot from all this.
Cheers,
Tim Tregubov
On Thu, 4 Jan 2001, Neil Long wrote:
> As a reference point....
>
> I just built 2.4.0 on an Indy 4600 IRIX 6.5.10m using the 7.2.1.2m C
> compiler and it all went to completion (lots of warnings but that is common
> with most packages).
>
> I just did a
> ./configure
> make
>
> I would suggest that you zap the ssh-2.4.0 directory and untar the src again
> and just try again on a fresh src tree.
>
> A make distclean is sometimes useful to ensure that all the leftovers are
> gone.
>
> regards
> Neil
>
>
> > Thanks!
> >
> > I've been trying out some of the things suggested but haven't yet been
> > successful...
> >
> > The linker command line:
> > /usr/lib32/cmplrs/ld32 -call_shared -no_unresolved -transitive_link -elf
> > -_SYSTYPE_SVR4 -g2 -L. -L../../lib -L/usr/local/lib -show -mips4 -n32
> > -L/usr/lib32/mips4/r10000 -L/usr/lib32/mips4 -L/usr/lib32
> > /usr/lib32/mips4/crt1.o -o ssh2 ssh2.o -lssh2 -lssh -ltermcap -lgen
> > -ltermcap -lm -lbsd -dont_warn_unused -Bdynamic -lc
> > /usr/lib32/mips4/crtn.o -warn_unused
> >
> > The ar line:
> > ar cru libssh2.a agentclient.o sshchagent.o sshserver.o agentpath.o
> > sshchsession.o sshstdiofilter.o authc-passwd.o sshchssh1agent.o
> > authc-pubkey.o sshchtcpfwd.o sshunixuserfiles.o auths-passwd.o sshchx11.o
> > sshuserfiles.o auths-pubkey.o auths-kerberos.o authc-kerberos.o
> > auths-kerberos-tgt.o authc-kerberos-tgt.o sshclient.o sshcommon.o
> > readpass.o sshconfig.o sshauthmethodc.o sshauthmethods.o sshglob.o
> > auths-common.o sshttyflags.o auths-hostbased.o authc-hostbased.o
> > auths-hostbased-rhosts.o ssh2pgppub.o ssh2pgpsec.o ssh2pgputil.o
> > sshappcommon.o sshfilecopy.o sshgetcwd.o sshfc_conn.o sshfc_glob.o
> > sshfc_overwrite.o sshfc_transfer.o sshfc_recurse.o sshserverprobe.o
> > auth-pam-common.o auths-pam.o authc-pam.o auths-securid.o authc-securid.o
> > ssh1encode.o ssh1keydecode.o
> > ranlib libssh2.a
> >
> > The cc line:
> > cc -n32 -D_LONG_LONG_LIMB -g -n32 -o ssh2 ssh2.o -L. -L../../lib -lssh2
> > -lssh -ltermcap -L/usr/local/lib -lgen -ltermcap -lm -lbsd
> > ld32: WARNING 126: etc etc etc
> >
> > If you still think it would help I can send the config.log file, its just
> > very large. :-)
> >
> > Thanks much for the help!
> >
> > Cheers,
> > Tim
> >
> >
> > On Thu, 4 Jan 2001, Sami Lehtinen wrote:
> >
> > > tims test account, on January 3. 2001, wrote:
> > > : I'm trying to compile SSH 2.4.0 on a bunch of SGI's most running
> 6.5(.10).
> > > : I'm not terribly familiar with SGI's being mostly a linux person
> myself,
> > > : but presented with this problem I'm trying to tackle it.
> > > :
> > > : Here's the prob when compiling:
> > > :
> > > : ld32: ERROR 33 : Unresolved text symbol "ssh_debug_enabled" -- 1st
> > > : referenced by ssh2.o.
> > > : Use linker option -v to see when and which objects, archives and
> > > [SNIP]
> > > :
> > > : etc... etc.. etc...
> > > :
> > > : I've tried it with both cc and gcc. with and without optimization...
> > > :
> > > : I've gotten this to compile fine on my Redhat7.0 and Digital Unix
> > > : machines.
> > > :
> > > : I've been looking through all sorts of newsgroups and archives and
> haven't
> > > : found a single helpful hint as to what I'm doing wrong...
> > > :
> > > : Any help would be greatly appreciated!!
> > >
> > > Please, could you send me the command line used to link the
> > > executable. It seems that the libssh.a (in lib/) isn't either
> > > correctly linked in or it has not been properly built. Also, the
> > > config.log file would probably help.
> > >
> > > Cheers,
> > >
> >
> >
>
>
