Date: Tue, 20 Nov 2007 10:23:30 -0500 From: Jerry McAllister <jerrymc@msu.edu> To: "Dan Mahoney, System Admin" <danm@prime.gushi.org> Cc: Jerry McAllister <jerrymc@msu.edu>, questions@freebsd.org Subject: Re: Build Frustrations Message-ID: <20071120152330.GA40738@gizmo.acns.msu.edu> In-Reply-To: <alpine.BSF.0.999.0711192209430.90095@prime.gushi.org> References: <20071119190959.V51743@prime.gushi.org> <20071120024955.GA38153@gizmo.acns.msu.edu> <alpine.BSF.0.999.0711192209430.90095@prime.gushi.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Nov 19, 2007 at 10:17:18PM -0500, Dan Mahoney, System Admin wrote: > On Mon, 19 Nov 2007, Jerry McAllister wrote: > > >On Mon, Nov 19, 2007 at 07:19:34PM -0500, Dan Mahoney, System Admin wrote: > > > >>All, > >> > >>I'm of the realization that FreeBSD is a volunteer project, but there's a > >>recent issue I've hit, and I've contacted nearly EVERYONE I can think of > >>about it to try and fix, and the response I've gotten has been a deafening > >>silence. > >> > >>I'm having trouble building apache2.2.6, it relates I feel to an > >>inconsitent libexpat library under FreeBSD, COMBINED with a badly made and > >>inconsistent apr port, and some libiconv incompatibilities. I've emailed > >>ports maintainers, APR developers, the general apache mailing list, and > >>gotten nothing. > >> > >>... > >> > >>This is a post about building apache2.2 from scratch, not from ports -- > >>however it raises several issues with port-installed tools that lead me to > >>believe they may still be at fault. I apologize in advance for the length > >>of this post, but having all the data is sometimes important. I believe > >>it's reproducable but I don't have the spare machines to try on. > >> > >>... > >> > >>3) My big problem: > >> > >> > >>I just tried to build apache 2.2.6 from scratch. > >> > >>I, for various reasons of wanting to keep apache separate from other > >>things, for example, to virtualize my apache users, prefer everything in a > >>single dir -- so the ports route isn't for me. > >> > > > >You can tell ports where to install something. We used to install > >all of Apache in its own directory to make it easy to manipulate > >in a system we were installing in a lot of places. Check the ports > >doc and such. > > *headdesk, repeatedly* > > Apache2 is a complete piece of crap. "Portable Runtime" my ass. Was > there something so wrong with APACI? Apache1.3 built out of the box on > every system in the world. > > Using ports is no better. And again, I'll take anything anyone can offer > to explain half this behavior: > I am using Apache 2.xx with no problem on several machines. I installed it from ports with no problem. Since you are determined to proceed against recommendations it is hard to help you. I wouldn't be surprised if you do not get many responses. ////jerry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071120152330.GA40738>