Date: Sat, 27 Nov 1999 15:44:19 -0500 (EST) From: matt@zigg.com To: FreeBSD-gnats-submit@freebsd.org Subject: ports/15123: www/apache13-modssl has PREFIX problems finding OpenSSL Message-ID: <199911272044.PAA75717@megaweapon.zigg.com>
next in thread | raw e-mail | index | archive | help
>Number: 15123
>Category: ports
>Synopsis: www/apache13-modssl has PREFIX problems finding OpenSSL
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-ports
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sat Nov 27 13:30:02 PST 1999
>Closed-Date:
>Last-Modified:
>Originator: Matt Behrens
>Release: FreeBSD 3.3-STABLE i386
>Organization:
zigg.com
>Environment:
FreeBSD megaweapon.zigg.com 3.3-STABLE FreeBSD 3.3-STABLE #2: Sat Nov 20 19:51:35 EST 1999 matt@megaweapon.zigg.com:/usr/src/sys/compile/MEGAWEAPON i386
>Description:
www/apache13-modssl has a problem finding OpenSSL which appears to
be PREFIX-related, but may also happen even if /usr/local is used
as the PREFIX. When the module is being configured it searches
for OpenSSL include files. It cannot find them because
${PREFIX}/include/openssl is not in its search path.
I suspect, but cannot confirm, that this would fail even if PREFIX
was not set because OpenSSL would then install its includes into
/usr/local/include/openssl, and the closest match to that in the
script's list is /usr/local/include/ssl.
In addition, this failure does not return an error code, which
would enable the ports system to detect that the configure had
failed. Rather, it marks .configure_done and happily moves right
along to the build phase, which of course does return an error
code.
>How-To-Repeat:
# cd /usr/ports/www/apache13-modssl
# make PREFIX=/foo/bar install
>Fix:
The port (or maybe source tarball?) needs to fix
work/mod_ssl-2.4.9-1.3.9/pkg.sslmod/libssl.module at line 343 to
include a reference to ${PREFIX}/include/openssl in its include
search. Of course this would probably be done with sed before
configure is called. However this port is somewhat complex and I
think the maintainer might have a better idea than I would how to
actually go about doing this.
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199911272044.PAA75717>