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. ////jerry _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
