Date: Fri, 12 Jun 1998 10:49:49 -0700 (PDT) From: kkennawa@physics.adelaide.edu.au To: freebsd-gnats-submit@FreeBSD.ORG Subject: ports/6930: socks5 port broken by /usr/lib/aout changes? Message-ID: <199806121749.KAA00208@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 6930 >Category: ports >Synopsis: socks5 port broken by /usr/lib/aout changes? >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-ports >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jun 12 10:50:03 PDT 1998 >Last-Modified: >Originator: Kris Kennaway >Organization: >Release: 3.0-CURRENT >Environment: FreeBSD morden.webmedia.com.au 3.0-CURRENT FreeBSD 3.0-CURRENT #1: Mon Jun 8 22:45:14 CST 1998 kkenn@morden.webmedia.com.au:/usr2/src/sys/compile/MORDEN i386 >Description: Recent /usr/lib/aout changes seem to have broken at least part of the socks5 port (/usr/ports/net/socks5). Specifically, the 'runsocks' command no longer seems to work - this command performs a runtime re-linking of executables to use the socks5 libraries and thus communicate through a socks5 proxy. >How-To-Repeat: Install port on a post-/usr/lib/aout machine, then attempt 'runsocks <cmd>' where <cmd> is a non-socks aware command, such as telnet (yeah, theres a rtelnet installed by the port, thats not the point :-) runsocks telnet immediately exits to the command line with no errors runsocks ftp hangs, refuses to respond to ^C or most other keystrokes Pre-aout changes, runsocks worked fine for me :) >Fix: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199806121749.KAA00208>