From owner-freebsd-ports@FreeBSD.ORG Mon Sep 20 23:14:32 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D23A6106564A for ; Mon, 20 Sep 2010 23:14:32 +0000 (UTC) (envelope-from steve@energistic.com) Received: from energistic.com (mail.energistic.com [216.54.148.60]) by mx1.freebsd.org (Postfix) with ESMTP id 9E61F8FC12 for ; Mon, 20 Sep 2010 23:14:32 +0000 (UTC) Received: from energistic.com (localhost [127.0.0.1]) by energistic.com (8.14.3/8.14.3) with ESMTP id o8KNERBh030859; Mon, 20 Sep 2010 19:14:27 -0400 (EDT) (envelope-from steve@energistic.com) Received: (from steve@localhost) by energistic.com (8.14.3/8.14.3/Submit) id o8KNERX3028821; Mon, 20 Sep 2010 19:14:27 -0400 (EDT) (envelope-from steve) Date: Mon, 20 Sep 2010 19:14:26 -0400 From: Steve Ames To: David Southwell Message-ID: <20100920231426.GA55891@energistic.com> References: <201009201028.38559.david@vizion2000.net> <337EAE2CBCD84FF49F376860EF1830F6@eservoffice.com> <201009202229.01038.david@vizion2000.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201009202229.01038.david@vizion2000.net> User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED,BAYES_50 autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on energistic.com Cc: mi@aldan.algebra.com, freebsd-ports@freebsd.org Subject: Re: ptlib build failure - breaks pwlib - hence also asterisk - opal - & openh323 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: Mon, 20 Sep 2010 23:14:32 -0000 On Mon, Sep 20, 2010 at 10:29:00PM +0100, David Southwell wrote: > >> Does SSL from ports declare something that we can #ifdef around? I > don't > > > really use pwlib anymore. If you can produce a patch that fixes your > issue > > > without breaking the case of using system openssl I'll happly give it > the > > > nod. ports/pwlib is very old. Everything should be moving to ports/ptlib > > > (2.4) or ports/ptlib26 > > Thanks for your reply. > > IMHO The problem is ptlibs AND ptlib26. Both these ports seem to be the > cause of the problem. pwlib tries to build ptlib and that build fails. > ptlib26 fails with the same error. > Actually not. pwlib _IS_ ptlib just a very old version. It doesn't build ptlib or ptlib26. > I think you have your finger on the pulse... both ptlib AND ptlib26 need > to address the way they use openssl but I do not know how to do that! Heh. Until someone who cares does know then its not likely to get fixed. As I said, I don't even use anymore so I have no test/develpment platform. > David > > PS Would you mind not top posting Seriously? Top posting is somehow worse than scrolling to the bottom of pages of compile output to see a tiny response? Welcome to the 21st century.