lighttpd does not pull OpenSSL dependency
kitche at kitchetech.com
Mon Oct 24 14:06:51 UTC 2016
This might be due to you had port installed already and it got picked up
On Oct 24, 2016 7:59 AM, "Guido Falsi" <mad at madpilot.net> wrote:
> On 10/24/16 13:15, David Demelier wrote:
> > Hello,
> > Upgraded my system to 11.0-RELEASE-p1 and using 2016Q4 branch, I have a
> > small issue regarding lighttpd dependency.
> > The binary is linked against the OpenSSL port, but it is not listed as a
> > dependency:
> > /usr/local/sbin/lighttpd:
> > libpcre.so.1 => /usr/local/lib/libpcre.so.1 (0x800854000)
> > libssl.so.8 => /usr/local/lib/libssl.so.8 (0x800acc000)
> > libcrypto.so.8 => /usr/local/lib/libcrypto.so.8 (0x800d3f000)
> > libc.so.7 => /lib/libc.so.7 (0x80114c000)
> > libthr.so.3 => /lib/libthr.so.3 (0x801500000)
> > What can I do to fix that?
> Are you generating your own packages? What software are you using to do
> Are you using some directive to enable ports provided ssl library?
> A machine using my own generated packages using poudriere does not show
> such behavior using ports trunk:
> libpcre.so.1 => /usr/local/lib/libpcre.so.1 (0x800857000)
> libssl.so.8 => /usr/lib/libssl.so.8 (0x800acf000)
> libcrypto.so.8 => /lib/libcrypto.so.8 (0x800e00000)
> libc.so.7 => /lib/libc.so.7 (0x80126d000)
> libthr.so.3 => /lib/libthr.so.3 (0x80160d000)
> A VM I have using official packages from 2016Q4 also gives the same
> output(apart from the offsets which are slightly different) when
> checking a just downloaded lighttpd package.
> So I'd conclude there's something wrong affecting your builds. What
> about a stray installation of a ports provided ssl library somewhere?
> More information will be needed to really help you.
> Guido Falsi <mad at madpilot.net>
> freebsd-ports at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
More information about the freebsd-ports