Date: Wed, 5 Mar 2003 12:42:48 +0200 From: Peter Pentchev <roam@ringlet.net> To: Scot Hetzel <hetzels@westbend.net> Cc: Stephen Cravey <clists@www.gotbrains.org>, ports@FreeBSD.ORG, dirk@FreeBSD.ORG Subject: Re: mod_php4.3.1 + CURL cores with apache13-modssl Message-ID: <20030305104248.GA439@straylight.oblivion.bg> In-Reply-To: <000301c2dfb0$f9b98b80$19fd2fd8@westbend.net> References: <20030228204239.X31300@www.gotbrains.org> <000301c2dfb0$f9b98b80$19fd2fd8@westbend.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--BXVAT5kNtrzKuDFl
Content-Type: text/plain; charset=windows-1251
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Feb 28, 2003 at 11:11:11PM -0600, Scot Hetzel wrote:
> From: "Stephen Cravey" <clists@www.gotbrains.org>
> > I seem to have discovered a problem with the mod_php4 4.3.1 port when it
> > interacts with CURL and apache13-modssl port. When CURL support is
> > compiled into php4 and the libssl/mod_ssl modules are loaded/added apac=
he
> > cores on startup. so basically, an 'apachectl startssl' result in :
> >
>=20
> > I believe that this may have something to do with a conflict between the
> > openssl 'port' libraries apache-modssl uses and the freebsd 'contrib'
> > openssl libraries that curl is using. I do not get an error when compil=
ing
> > curl, only mod_php4. I do not understand the linker well enough to fully
> > understand where precicely the problem might lie.
> >
>=20
> The apache-modssl port includes a file from the security/openssl port, th=
ats
> used to select either the base OpenSSL or the Port OpenSSL. This is what=
is
> causing the apache-modssl to use the OpenSSL port when it is installed.
>=20
> > php4 'make' with curl support during the curl support (not curl
> > port) build section shows:
> >
> > /usr/libexec/elf/ld: warning: libssl.so.2, needed by
> > /usr/local/lib/libcurl.so, may conflict with libssl.so.3
> >
> > /usr/libexec/elf/ld: warning: libcrypto.so.2, needed by
> > /usr/local/lib/libcurl.so, may conflict with libcrypto.so.3
> >
>=20
> > curl-7.10.3_1
> You need to modify the ftp/curl/Makefile and add the following under the
> !defined(WITHOUT_SSL).
>=20
> .include "${PORTSDIR}/security/openssl/Makefile.ssl"
>=20
> Give this a try, and let roam@FreeBSD.org know if this fixes your problem.
I just committed an update to the ftp/curl port, now at 7.10.3_2,
which uses security/openssl/Makefile.ssl instead of USE_OPENSSL.
Thanks for pointing this out!
G'luck,
Peter
--=20
Peter Pentchev roam@ringlet.net roam@sbnd.net roam@FreeBSD.org
PGP key: http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553
This sentence is false.
--BXVAT5kNtrzKuDFl
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)
iD8DBQE+ZdSo7Ri2jRYZRVMRAu0kAJ0ZsZoTcZTlDtf8DX2dhJ1BG0xs1ACbBBZA
DMNYqBYBrTYXkjO5xif1lOI=
=KIsJ
-----END PGP SIGNATURE-----
--BXVAT5kNtrzKuDFl--
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?20030305104248.GA439>