Compiling MySecureShell on SCO 6.0


 
Thread Tools Search this Thread
Operating Systems SCO Compiling MySecureShell on SCO 6.0
# 1  
Old 02-01-2010
Compiling MySecureShell on SCO 6.0

I downloaded the source, vsn 1.15 from SourceForge, and ran configure, and then tried make.
I got the following errors:

Quote:
Undefined first referenced
symbol in file
gethostbyaddr ip.o
inet_addr ip.o
gethostbyname parsing.o
UX:ld: ERROR: Symbol referencing errors. No output written

I tried fixing it by setting LD_LIBRARY_PATH to /usr/lib, and by adding -lsocket to the CFLAGS in the make file. But this made no difference.

gethostbyaddr, gethostbyname and inet_addr are all in /usr/lib/libsocket.so

---------- Post updated at 10:18 PM ---------- Previous update was at 07:58 PM ----------

I adjusted the Makefile, and eventually it compiled clean. There are some directory differences as well; I edited one of the header files. I also had to modify the default sftp_config file.
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Cybersecurity

MySecureShell 1.15

Hello, We use MySecureShell 1.15 to chroot our users when using SFTP. Has anyone heard of any security issues using this software? We want to lock down any potential security issues. Thanks. (0 Replies)
Discussion started by: mojoman
0 Replies
Login or Register to Ask a Question
AS(1)							      General Commands Manual							     AS(1)

NAME
as - assembler SYNOPSIS
as [ - ] [ -o objfile ] file ... DESCRIPTION
As assembles the concatenation of the named files. If the optional first argument - is used, all undefined symbols in the assembly are treated as global. The output of the assembly is left on the file objfile; if that is omitted, a.out is used. It is executable if no errors occurred during the assembly, and if there were no unresolved external references. FILES
/lib/as2 pass 2 of the assembler /tmp/atm[1-3]? temporary a.out object SEE ALSO
ld(1), nm(1), adb(1), a.out(5) UNIX Assembler Manual by D. M. Ritchie DIAGNOSTICS
When an input file cannot be read, its name followed by a question mark is typed and assembly ceases. When syntactic or semantic errors occur, a single-character diagnostic is typed out together with the line number and the file name in which it occurred. Errors in pass 1 cause cancellation of pass 2. The possible errors are: ) Parentheses error ] Parentheses error < String not terminated properly * Indirection used illegally . Illegal assignment to `.' a Error in address b Branch instruction is odd or too remote e Error in expression f Error in local (`f' or `b') type symbol g Garbage (unknown) character i End of file inside an if m Multiply defined symbol as label o Word quantity assembled at odd address p `.' different in pass 1 and 2 r Relocation error u Undefined symbol x Syntax error BUGS
Syntax errors can cause incorrect line numbers in following diagnostics. PDP11 AS(1)