Date: Thu, 8 Jun 2006 17:20:18 GMT From: Dan Lukes <dan@obluda.cz> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/98525: [ PATCH ] net/freeradius didn't use non BASE OpenSSL (from ports) Message-ID: <200606081720.k58HKIbM054409@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/98525; it has been noted by GNATS. From: Dan Lukes <dan@obluda.cz> To: pav@FreeBSD.org Cc: bug-followup@FreeBSD.org, kris@obsecurity.org Subject: Re: ports/98525: [ PATCH ] net/freeradius didn't use non BASE OpenSSL (from ports) Date: Thu, 08 Jun 2006 17:30:07 +0200 Pav Lucistnik napsal/wrote, On 06/08/06 14:54: > What about skipping these modules on 4.X with base OpenSSL? It need depth evaluation. The package has no single configure - modules has it's own configure scripts and it's logic related to openssl seems not to be so consistent - at least on FreeBSD 4 with base OpenSSL. We need to be sure it reject or accept OpenSSL consistently for all compiled components. Even the port is successfully compiled and packaged, it may not be runnable because some symbols may be required by one component (which wish the OpenSSL is present) but not present in other component (which detects no OpenSSL in system). The PR 98525 (this PR) reports this kind of problem. Unfortunately, all my 4.x system are production system with PORT's OpenSSL installed (because the BASE OpenSSL is broken), so I can't do required tests on BASE only system. Your way may be better if you can evaluate all consequences. My way is just hack - it should work in all cases but it's suboptimal on some. Kris Kennaway napsal/wrote, On 06/08/06 15:31: > Please verify that it's not broken in the same way on other versions too. The committed patch should not broke the compilation on 5.x and 6.x with base OpenSSL as supplied parameters are the same as auto detected. On 4.x, 5.x, 6.x with PORT OpenSSL it should work also. The only problematic configuration should be 4.x with BASE OpenSSL due malfunction of freeradius configure system. Well, it's theory, I know. I sucesfully compiled and created package on: 1. 6-STABLE, no PORT OpenSSL 2. 6-STABLE, PORT OpenSSL 3. 4.11-RELEASE-p18, PORT OpenSSL No try to configure and run it on my side with exception of [3] which successfully runs on production server. Dan -- Dan Lukes SISAL MFF UK AKA: dan@obluda.cz, dan@freebsd.cz,dan@kolej.mff.cuni.cz
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200606081720.k58HKIbM054409>