Date: Mon, 01 May 2017 11:43:45 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 218688] [patch] graphics/mupdf links with ssl if a pkgconfig for libcrypto exists Message-ID: <bug-218688-13-Chec2VaC5H@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-218688-13@https.bugs.freebsd.org/bugzilla/> References: <bug-218688-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218688 --- Comment #2 from Zsolt Udvari <udvzsolt@gmail.com> --- Your patch isn't good. If you add simply "USES+=3Dssl" it means that mupdf wants to use SSL base (/usr/lib/libcrypto.so) and doesn't trigger to install libre/openssl. And in this case you don't have any ssl-specific pkg-config file so the mup= df's test will fail. I think we have two choices: - full disable the ssl (patch the ssl-test in Makerules) - use the system's ssl (patch the ssl-test and SYS_LIBCRYPTO_{CFLAGS,LIBS}) Or an another choice: - use libre/openssl - but I don't want it because I've an idea to more work= on mupdf port: print/cups-client now requires mupdf so the install of cups-cli= ent requires many Xorg-libraries (if you've a printserver you don't want many Xorg-libraries). My opinion: the full disable because there isn't any bug report (feature request) about missing ssl in mupdf. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-218688-13-Chec2VaC5H>