We have found a fix that will change the building of librsaUSA to fix the
problem. The fix will get committed after the release engineer approve the
commit. The port will not need to be changed in the long run.
Jim Bloom
[EMAIL PROTECTED]
Jim Bloom wrote:
>
> You definitely don't need -lRSAgl
I am seeing the same thing with a world built yesterday afternoon. I
don't know if this is an issue with multiple dlopen'ed libraries or
what. Here is what I believe the port is doing. During the build
process, the main apache server is built. The ssl layer is created as
an add-in module (.so)
At 07:56 PM 2/29/2000 -0800, Kris Kennaway wrote:
>On Tue, 29 Feb 2000, Manfred Antar wrote:
>
> > I needed to add -lRSAglue -lrsaUSA to the SSL_LIBS= line in
> > /usr/ports/www/apache13-php3/work/apache_1.3.12/src/modules/ssl/Makefile
> > and install the recompiled libssl.so in /usr/local/libexe
At 07:56 PM 2/29/2000 -0800, you wrote:
>On Tue, 29 Feb 2000, Manfred Antar wrote:
>
> > I needed to add -lRSAglue -lrsaUSA to the SSL_LIBS= line in
> > /usr/ports/www/apache13-php3/work/apache_1.3.12/src/modules/ssl/Makefile
> > and install the recompiled libssl.so in /usr/local/libexec/apache.
On Tue, 29 Feb 2000, Manfred Antar wrote:
> I needed to add -lRSAglue -lrsaUSA to the SSL_LIBS= line in
> /usr/ports/www/apache13-php3/work/apache_1.3.12/src/modules/ssl/Makefile
> and install the recompiled libssl.so in /usr/local/libexec/apache.
> Works fine
> Note this is for the apache13-php
You definitely don't need -lRSAglue. That file is an empty library just for
compatibility.
The port apache3-modssl worked a couple days ago when I last made a pass through
all of the ports using openssl in -current. I'll take a look at it again (by
tomorrow) and see where things stand. The rec
On Tue, Feb 29, 2000 at 07:26:53PM -0800, Manfred Antar wrote:
> I needed to add -lRSAglue -lrsaUSA to the SSL_LIBS= line in
> /usr/ports/www/apache13-php3/work/apache_1.3.12/src/modules/ssl/Makefile
> and install the recompiled libssl.so in /usr/local/libexec/apache.
> Works fine
> Note this is
At 12:00 PM 2/29/2000 -0800, Sean-Paul Rees wrote:
>I'm having a problem getting Apache setup to work with modssl; I'm running
>apache1.3.12+php4+mod_ssl2.6.0
>
>[root@valiant]-~# apachectl startssl
>/usr/local/sbin/apachectl startssl: httpd could not be started
>
>No other info whatsoever. (helpf
On Tue, 29 Feb 2000, Bush Doctor wrote:
> > Make sure the contents of secure/lib are up-to-date. Having an old or out
> > of sync version of libcrypto could cause this.
> Hmmm ...
> This does not seem to be the case:
Yeah, but have you rebuilt them? ;)
Kris
In God we Trust -- all others m
Out of da blue Kris Kennaway aka ([EMAIL PROTECTED]) said:
> On Tue, 29 Feb 2000, Bush Doctor wrote:
>
> > > No other info whatsoever. (helpful, huh? :-)
> > I've run into the same problem. You'll probably see this in
>/var/log/apache_error_log
> > /usr/libexec/ld-elf.so.1: /usr/lib/librsaUSA.s
On Tue, 29 Feb 2000, Bush Doctor wrote:
> > No other info whatsoever. (helpful, huh? :-)
> I've run into the same problem. You'll probably see this in
>/var/log/apache_error_log
> /usr/libexec/ld-elf.so.1: /usr/lib/librsaUSA.so: Undefined symbol "ERR_load_strings"
> /usr/libexec/ld-elf.so.1: /u
Out of da blue Sean-Paul Rees aka ([EMAIL PROTECTED]) said:
> I'm having a problem getting Apache setup to work with modssl; I'm running
> apache1.3.12+php4+mod_ssl2.6.0
>
> [root@valiant]-~# apachectl startssl
> /usr/local/sbin/apachectl startssl: httpd could not be started
>
> No other info what
I'm having a problem getting Apache setup to work with modssl; I'm running
apache1.3.12+php4+mod_ssl2.6.0
[root@valiant]-~# apachectl startssl
/usr/local/sbin/apachectl startssl: httpd could not be started
No other info whatsoever. (helpful, huh? :-)
I'm using the stock configuration file with
13 matches
Mail list logo
