From owner-freebsd-ports  Fri Jun 12 10:51:26 1998
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA00589
          for freebsd-ports-outgoing; Fri, 12 Jun 1998 10:51:26 -0700 (PDT)
          (envelope-from owner-freebsd-ports@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00443
          for <freebsd-ports@FreeBSD.org>; Fri, 12 Jun 1998 10:50:40 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id KAA21723;
	Fri, 12 Jun 1998 10:50:03 -0700 (PDT)
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA00208;
          Fri, 12 Jun 1998 10:49:49 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199806121749.KAA00208@hub.freebsd.org>
Date: Fri, 12 Jun 1998 10:49:49 -0700 (PDT)
From: kkennawa@physics.adelaide.edu.au
To: freebsd-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: www-1.0
Subject: ports/6930: socks5 port broken by /usr/lib/aout changes?
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>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