Date: Mon, 24 Oct 2016 20:55:08 +0200 From: Guido Falsi <mad@madpilot.net> To: David Demelier <demelier.david@gmail.com> Cc: freebsd-ports@freebsd.org Subject: Re: lighttpd does not pull OpenSSL dependency Message-ID: <da9e1a6b-0db1-ff18-08b6-82bbd0ab0101@madpilot.net> In-Reply-To: <CAO%2BPfDeMzyPxJc1m7eVPfFTgD=nvwyiS=o-CewEFAi7znSwN=Q@mail.gmail.com> References: <2f756004-b35c-b9df-bcec-af596b100edb@gmail.com> <b2386423-3d24-5843-7dc2-7976ff14cb93@madpilot.net> <CAO%2BPfDeMzyPxJc1m7eVPfFTgD=nvwyiS=o-CewEFAi7znSwN=Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/24/16 16:28, David Demelier wrote: > 2016-10-24 14:59 GMT+02:00 Guido Falsi <mad@madpilot.net>: >> Are you generating your own packages? What software are you using to do >> that? > > Yes, I'm using poudriere. However I didn't upgrade poudriere for a > while, maybe I should upgrade it too. The bulk build was clean at time > I ran it, since it was an upgrade no packages were existing. It culd be related. It's at least worth a try. > >> Are you using some directive to enable ports provided ssl library? > > If you mean some tunables in the make.conf files, no. > >> So I'd conclude there's something wrong affecting your builds. What >> about a stray installation of a ports provided ssl library somewhere? > > I'm not sure to understand your question. The bulk build was clean (no > package existing), I'll double check this evening if removing the > lighttpd package to force a rebuild will fix that. > I see but for some reason the port, while building, picked up a ports provided openssl library, it had to be there somehow for the port to pick that up. I have no idea how it could be there though. -- Guido Falsi <mad@madpilot.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?da9e1a6b-0db1-ff18-08b6-82bbd0ab0101>