Date: Mon, 20 Sep 2010 19:14:26 -0400 From: Steve Ames <steve@energistic.com> To: David Southwell <david@vizion2000.net> Cc: mi@aldan.algebra.com, freebsd-ports@freebsd.org Subject: Re: ptlib build failure - breaks pwlib - hence also asterisk - opal - & openh323 Message-ID: <20100920231426.GA55891@energistic.com> In-Reply-To: <201009202229.01038.david@vizion2000.net> References: <201009201028.38559.david@vizion2000.net> <337EAE2CBCD84FF49F376860EF1830F6@eservoffice.com> <201009202229.01038.david@vizion2000.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100920231426.GA55891>