Date: Fri, 29 Jun 2007 12:53:47 -0700 (PDT) From: Jeff Roberson <jroberson@chesapeake.net> To: Joe Marcus Clarke <marcus@marcuscom.com> Cc: gnome@freebsd.org Subject: Re: firefox port lacks ssl support? Message-ID: <20070629125300.R552@10.0.0.1> In-Reply-To: <1183146171.53232.29.camel@shumai.marcuscom.com> References: <20070629003214.E552@10.0.0.1> <1183133343.53232.0.camel@shumai.marcuscom.com> <20070629122704.O552@10.0.0.1> <1183146171.53232.29.camel@shumai.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 29 Jun 2007, Joe Marcus Clarke wrote: > On Fri, 2007-06-29 at 12:28 -0700, Jeff Roberson wrote: >> On Fri, 29 Jun 2007, Joe Marcus Clarke wrote: >> >>> On Fri, 2007-06-29 at 00:33 -0700, Jeff Roberson wrote: >>>> I recently updated my world and neither firefox or seamonkey support >>>> https. Is this a known problem? >>>> >>>> firefox-2.0.0.4,1 Web browser based on the browser portion of Mozilla >>>> seamonkey-1.1.2 The open source, standards compliant web browser >>>> >>>> Those are my ports versions. >>> >>> Rebuild devel/nspr and security/nss, then rebuild Firefox. >> >> Thanks, should this go in the ports UPDATING? > > We typically require people to use portupgrade, and keep their whole > ports tree up-to-date. I actually did that. Kris helped me with update with Xorg and I forced all new packages using portupgrade. > > Joe > > -- > PGP Key : http://www.marcuscom.com/pgp.asc >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070629125300.R552>