From owner-freebsd-ports@FreeBSD.ORG Fri Dec 29 18:16:54 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 8D69516A403 for ; Fri, 29 Dec 2006 18:16:54 +0000 (UTC) (envelope-from durian@shadetreesoftware.com) Received: from mailhost.boogie.com (mailhost.boogie.com [70.91.170.29]) by mx1.freebsd.org (Postfix) with ESMTP id 3D92313C441 for ; Fri, 29 Dec 2006 18:16:54 +0000 (UTC) (envelope-from durian@shadetreesoftware.com) Received: from man.boogie.com (man.boogie.com [192.168.1.3]) by mailhost.boogie.com (8.13.8/8.13.8) with ESMTP id kBTHeUqt003820 for ; Fri, 29 Dec 2006 10:40:30 -0700 (MST) (envelope-from durian@shadetreesoftware.com) From: Mike Durian Organization: Shade Tree Software, LLC To: freebsd-ports@freebsd.org Date: Fri, 29 Dec 2006 10:40:29 -0700 User-Agent: KMail/1.9.4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200612291040.29615.durian@shadetreesoftware.com> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (mailhost.boogie.com [70.91.170.29]); Fri, 29 Dec 2006 10:40:30 -0700 (MST) X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.1.7 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on fever.boogie.com Subject: 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 18:16:54 -0000 I'm trying to build sipX (http://www.sipfoundry.org/sipX) under FreeBSD. Things are going smoothly, albeit slowly, for the most part, though I have just run into one problem related to the www/libwww port. 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? Also, if anyone is interested in making a port out of sipX, I would be glad to share my notes and patches. I'm just building it to test some SIP stuff and I'm not willing to commit to supporting the port myself, but I would be glad to assist anyone who is. Thanks, mike