From owner-freebsd-ports  Tue Sep 22 21:56:53 1998
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA01159
          for freebsd-ports-outgoing; Tue, 22 Sep 1998 21:56:53 -0700 (PDT)
          (envelope-from owner-freebsd-ports@FreeBSD.ORG)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA01145;
          Tue, 22 Sep 1998 21:56:39 -0700 (PDT)
          (envelope-from imp@village.org)
Received: from harmony [10.0.0.6] 
	by rover.village.org with esmtp (Exim 1.71 #1)
	id 0zLgyU-0000kG-00; Tue, 22 Sep 1998 22:56:22 -0600
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id WAA11754; Tue, 22 Sep 1998 22:56:38 -0600 (MDT)
Message-Id: <199809230456.WAA11754@harmony.village.org>
To: ports@FreeBSD.ORG
Cc: jdp@FreeBSD.ORG
Subject: SOCKS port inspires question...
Date: Tue, 22 Sep 1998 22:56:38 -0600
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


OK.  The SOCKS5 port is broken currently under elf.  No one seems to
have noticed this at all, which leads me to believe that it isn't as
popular a port as netscape...  :-)

Anyway, since I'm the maintainer and I use socks, I thought I'd dig
into the problems with it.  jdp was kind enough to accelerate his
implementation of LD_PRELOAD for ELF.  I've managed to get the port
working for ELF.  However, I have several questions that I don't think
have been addressed before.

First, how do I know tell at compile time what the object format for
the port is?  It seems to make a difference for symbol lookup in
dlsym.  I have some mail into jdp that I just sent, so this might not
be a problem.

Second, socks seems to be unique in that it has a runsocks command.
This command is unique, afaik, in that it sets LD_PRELOAD and runs the
reset of the command line.  This works great when you have just one
binary format on your system, but buys the large agricultural land
area when presented with an AOUT binary with a ELF library.  Moving
the AOUT library to the standard place (/usr/local/lib ->
/usr/local/lib/aout) doesn't solve this problem because we set
LD_PRELOAD to be libsocks5_sh.so and LD_LIBRARY_PATH to
/usr/local/lib:${LD_LIBRARY_PATH}.  The only way I see to fix it would
be to do a file on the command, then try to jigger the path based on
the file type.  Thinking about this for a moment tells me this won't
work on -stable or a aout system, so I'd also have to check the
libsocks5_sh.so as well.  Yuck!

So my second question is , should I bother with these relatively nasty
edge cases?  What are other ports doing in this area?  I've been a
slug and haven't been keeping up with ports traffic lately due to work
cutting into my mailing list reading time :-)

Comments?

Warner

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message