From owner-freebsd-ports@FreeBSD.ORG Fri Dec 29 19:19:58 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B303D16A47C for ; Fri, 29 Dec 2006 19:19:58 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.200.82]) by mx1.freebsd.org (Postfix) with ESMTP id 7A8E013C461 for ; Fri, 29 Dec 2006 19:19:58 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from icarus.home.lan (c-67-174-220-97.hsd1.ca.comcast.net[67.174.220.97]) by comcast.net (sccrmhc12) with ESMTP id <20061229190955012004hnk8e>; Fri, 29 Dec 2006 19:09:55 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id E13CE1FA037; Fri, 29 Dec 2006 11:09:54 -0800 (PST) Date: Fri, 29 Dec 2006 11:09:54 -0800 From: Jeremy Chadwick To: Mike Durian Message-ID: <20061229190954.GA84882@icarus.home.lan> Mail-Followup-To: Mike Durian , freebsd-ports@freebsd.org References: <200612291040.29615.durian@shadetreesoftware.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200612291040.29615.durian@shadetreesoftware.com> X-PGP-Key: http://jdc.parodius.com/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-ports@freebsd.org Subject: Re: www/libwww and SSL X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Dec 2006 19:19:58 -0000 On Fri, Dec 29, 2006 at 10:40:29AM -0700, Mike Durian wrote: > One of the sipX components wants to link againt libwwwssl.so. I believe > libwwwssl should come from the www/libwww port, but the port does not > enable this by default. Nor does there appear to be a configuration > knob that will enable it. I haven't been able to find an alternate > port that builds libwwwssl either (though maybe I didn't look hard > enough). > > I can enable it myself by adding --with-ssl to CONFIGURE_ARGS, but I'm > wondering if that is a good thing to do. Is www/libwww built without > SSL support for a reason (security, buggy, etc.), or is it just an > oversight? If it is an oversight, should --with-ssl become part > of the default configure args for www/libwww? Or at least have a > knob added to the Makefile? The current maintainer of this port is... no one! :-) Which means, if you could submit a patch, that'd be great. Keep in mind that the change involved will require more than just a simple Makefile tweak. You will also need to update pkg-plist to keep track of the extra libraries installed, any extra documentation, or utilities as a result of --with-ssl. Since there's a shared library involved, you should also use USE_LDCONFIG=yes to update the ld.so cache. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |