Date: Fri, 20 Dec 1996 10:32:57 -0500 (EST) From: Jeremy Sigmon <jsigmon@www.hsc.wvu.edu> To: Jon <jon@minotaur.net> Cc: freebsd-ports@freebsd.org Subject: Re: apache ports in current is broken Message-ID: <Pine.BSF.3.91.961220102944.12659C-100000@www.hsc.wvu.edu> In-Reply-To: <Pine.BSF.3.95.961220024754.996A-100000@shell.minotaur.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> > I was trying to install Apache with the SSL modifications and could not > get anything to work out whenever I set SECURE_SERVER so I would be able > to compile Apache with SSL support. > > I have already successfully compiled SSLeay from ports-current with > 2.2-ALPHA and am trying to get Apache to work. So far the only thing that > works is the regular version of Apache -- not the SSL one. I tried to > apply the patches manually but all the chunks failed with or without the > regular patches. > > If this could be fixed/updated and someone emails me as I dont subscribe > to ports, then I'd appreciate it. > I got this to work, but I didn't document what I did. :( #1 remove ALL extra stuff from the apache modules config. no DNS_MAXIMUM or ANY of that extra stuff. If you want it you will need to fix it since SSL changes some apache internals. Once you (finally) get a compile then you get to play with the certifications in SSL. Also if you are getting any error messages from apache-ssl you can look them up at strongholds web site since they use the same code and same error messages. Thats how I finally fixed mine. :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.961220102944.12659C-100000>