Re: Build Frustrations
-segmentation fault-
press any key to reboot
Damn damn damn [EMAIL PROTECTED] said, after restarting his
Date: Tue, 20 Nov 2007 00:44:36 -0600
From: Paul Schmehl [EMAIL PROTECTED]
Subject: Re: Build Frustrations
--On November 19, 2007 11:00:44 PM -0500 Dan Mahoney, System Admin
[EMAIL PROTECTED] wrote:
On Mon, 19 Nov 2007, Jerry McAllister wrote:
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.
Actually, I just tried this. This is not what I want.
If I go to cd /usr/ports/www/apache22, and do a make
PREFIX=/some/other/directory, I do NOT get the same thing
I'd get building apache from source. I get ALL the apache
prerequisites installed under /some/other/dir, as opposed
to the apache standards places (for example config files
which would normally be in /usr/local/apache/conf now get
installed in /some/other/directory/etc (the port installs
them in /usr/local/etc). As a bonus, dependent packages get
added to my package database under the same prefix, which
shouldn't happen. (i.e. I want ONLY the apache2.2 stuff in a
self-contained directory).
Silly me. I had no idea there was a standard place for
apache to put its stuff. On *some* linux builds, the conf
files are in /etc/httpd/conf.d/ and the document root in
/var/www. On FreeBSD they're in /usr/local/etc/apache{ver.}
and /usr/local/www/apache{ver}, respectively. What's the
standard place I wonder? I suspect it has a lot more to do
with the conventions of the particular OS than it does with the
application.
And on a SuSE system I've been called in to maintain the
webserver is on /srv/www while the conf files are in
/etc/httpd/httpd.conf.
About the only thing you can count on is that the files will be
somewhere on the system, and hopefully in your $PATH.
If the OP would take a look at 'man hier' he would see
how all of the FreeBSD things should be laid out.
Having things under /usr - instead of the top directory which it
appears the OP has as he said he wanted one directory - will
make upgrades a bit more difficult.
One of the nice things about keeping just the OS on / and
all other addons on a /usr filesystem is that you can unmount
/usr and rebuild the entire OS, remaking / is you wish, and lose
nothing of your local addons. It's a very intelligent design
IMO and it frustrates me when I got to different Linux systems [I
run FreeBSD at the ISP] and so many things are in different places.
It seems that some do this just ot differentiate them. But then
again I have not looked at all 300+ Linux distros. At least
the BSD derived variants are remarkable similar - and follow most
the same hierarchy for the past 20 years.
If the user weren't so set on just one filesystem [which is how I
remember the first part of the thread starting] he'd be running
now. And woe be the day that / gets corrupted with everything
in one place. My worsts instances of this was years ago when
data had to be saved, and / could be mounted ro as therw
was no lost+found space left. [The old SysIII and SySV system
could not expand lost+found].
So I spend the next 3 days running / in ro mode and then copying
and/or taring the needed data onto floppies for restore once the
OS was reinstalled. After maintaing Unix system [ and variants] on
a least 6 different CPU bases since 1983 - I'm hard-coded to
having separate file systems.
Never turn your back on a running computer.
Bill
--
Bill Vermillion - bv @ wjv . com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Build Frustrations
On Tue, 20 Nov 2007, Jerry McAllister wrote: 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. You know, there was a time when the handbook and man security actually recommended NOT using the port and building from scratch -- and if you want the finest-grained control over what you're building this is still the case, especially when some features haven't made it into ports yet. (Like, oh...when the whole of the ports tree goes into a freeze for a release that's upcoming but doesn't have a todo list, a schedule, or anything else on the FBSD site). Actually, someone (two different someones) managed to answer both issues. The ports issue was caused by stale cruft in /var/db/pkg and the fix was to remove basically all the automake/autotools/autoconf packages and start over. I also said screw it and nuked the apr-db42 port (for reasons mentioned earlier). Apache from ports then built fine (which meant I had an option to fall back on, if need be). Someone on the APR-devel list pointed out that I can do a setenv to define CFLAGS and LDFLAGS to include /usr/local/lib to fix build issues. This allowed apache2-non-ports to compile. However the question in my mind that still bears answering is: why apr would FIND such a library as installed (i.e. not fail at configure-time) but then fail to compile. I.e. why does the APR not set CFLAGS and LDFLAGS correctly. This is not a question for -questions, but I'm stating it here in case anyone has similar issues. -Dan -- Is Gushi a person or an entity? Yes -Bad Karma, August 25th 2001, Ezzi Computers, Quoting himself earler, referring to Gushi Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Build Frustrations
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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Build Frustrations
I don't have the correct computer in front of me at the moment, but I used to do this DAILY with 1000 different combinations of perl, apr, httpd, mod_perl. Its a bit dated at the moment, but it definitely will send you in the correct direction. And yes, this is on FreeBSD (at the time it was 6.1) http://p6m7g8.net/LA.pm/compile.sh.txt FWIW, The ASF itself doesn't use the FreeBSD port though apache.org is a FreeBSD box, but thats only because they will always have never versions before the ports tree. -- Philip M. Gollucci ([EMAIL PROTECTED]) o:703.549.2050x206 Senior System Admin - Riderway, Inc. http://riderway.com / http://ridecharge.com 1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB B89E 1324 9B4F EC88 A0BF Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Build Frustrations
This allowed apache2-non-ports to compile. However the question in my mind that still bears answering is: why apr would FIND such a library as installed (i.e. not fail at configure-time) but then fail to compile. I.e. why does the APR not set CFLAGS and LDFLAGS correctly. This you should post to [EMAIL PROTECTED], I might even answer it there, but the answer lies in the configure script logic which was chosen very carefully. -- Philip M. Gollucci ([EMAIL PROTECTED]) o:703.549.2050x206 Senior System Admin - Riderway, Inc. http://riderway.com / http://ridecharge.com 1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB B89E 1324 9B4F EC88 A0BF Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Build Frustrations
On Tue, 20 Nov 2007, Philip M. Gollucci wrote: This allowed apache2-non-ports to compile. However the question in my mind that still bears answering is: why apr would FIND such a library as installed (i.e. not fail at configure-time) but then fail to compile. I.e. why does the APR not set CFLAGS and LDFLAGS correctly. This you should post to [EMAIL PROTECTED], I might even answer it there, but the answer lies in the configure script logic which was chosen very carefully. I have done so. Also, I think I can confirm that if I unsetenv those two variables my build will again fail -- if you have additional commands you'd like me to run, for diagnostic or testing purposes -- or hell, if you want a shell, please just let me know. -Dan Mahoney -- You're a nomad billygoat! -Juston, July 18th, 2002 Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Build Frustrations
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. I'm posting this to the straight-off questions list because I feel my other attempts have failed. Can someone sanity check me? I'm well aware of how to ask intelligent questions, to document what I have and have not done, of explaining WHY I have or have not done those things. I'm going to send it here, in the hopes maybe someone else has encountered this or might spot something I'm missing. If ANYONE can shed some light here, I'd appreciate it and am willing to compensate in some small way, if I can. Here's what I sent to the maintainers of the above two ports: Subject: apr versus apr-db42, as well as some other issues: Hello, First and foremost: I assume you're both reasonably busy professionals. That said, I believe there's either a bug in the core operating system here, or a bug in the way some of the critical ports are built, and I cannot figure it out alone. It is enough of a problem that it has confused at least one apache committer. That said, if you'd like to be compensated in some small way for your time, please point me to your amazon wishlists, paypal accounts, et cetera, and I'll try to do the right thing. I am mailing you because you are the maintainers of the apache-2.2.6 and apr ports. If there are other people I should be mailing, please let me know. 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. First, the basics: 1) Is it possible to get some documentation in either the short or long description as to what the difference between apr and apr-db42 is? 2) Also, is it at all possible to get some kind of documentation for the apr-svn port (if it still exists). 3) My big problem: (I'm going to post everything from here down to the apache-users mailing list, as well). 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. Because apr-db42 had been installed as part of a subversion requirement (not sure why), it caused my apache build to look in nonexistent places for libraries. %apr-1-config --apr-libtool /usr/local/build-1/libtool (the above path doesn't even exist) To fix this (and not break the svn port), I resorted to using --with-included-apr. The build THEN failed, claiming it could not find the installed expat libraries, in an error exactly like what this gentleman had: http://www.zulustips.com/2007/10/06/problems-compiling-apache-226-on-freebsd-62.html#more-54 And in fact, this apache developer had the same issue: http://www.mail-archive.com/[EMAIL PROTECTED]/msg18793.html (search the page for wtf) Like them, I had an installed expat, and had it listed in ldconfig -r (I also note there's a libexpat in /usr/src but don't know what it's there for). (I did not copy my errors because I thought I had found a solution, but it's the same error, I assure you). After that, I tried resorting to building apache with --with-expat=builtin I then got THIS error: /home/danm/httpd-2.2.6/srclib/apr/libtool --silent --mode=link gcc -g -O2 -o htpasswd htpasswd.lo -lm /home/danm/httpd-2.2.6/srclib/pcre/libpcre.la /home/danm/httpd-2.2.6/srclib/apr-util/libaprutil-1.la /home/danm/httpd-2.2.6/srclib/apr-util/xml/expat/lib/libexpat.la /home/danm/httpd-2.2.6/srclib/apr/libapr-1.la -lcrypt -lpthread /home/danm/httpd-2.2.6/srclib/apr-util/.libs/libaprutil-1.so: undefined reference to `libiconv_open' /home/danm/httpd-2.2.6/srclib/apr-util/.libs/libaprutil-1.so: undefined reference to `libiconv_close' /home/danm/httpd-2.2.6/srclib/apr-util/.libs/libaprutil-1.so: undefined reference to `libiconv' *** Error code 1 Stop in /home5/danm/httpd-2.2.6/support. *** Error code 1 Stop in /home5/danm/httpd-2.2.6/support. *** Error code 1 Stop in /home5/danm/httpd-2.2.6. prime# So that's it. I don't know how to fix this one -- and if it's upgrading my libiconv will fix it (but will require me to upgrade every program -- both binary and port) that depends on it, I'm willing, but pkg_info -f -g
RE: Build Frustrations
This may help: http://lists.freebsd.org/pipermail/freebsd-stable/2004-December/010425.h tml Cheers, Brent -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan Mahoney, System Admin Sent: Tuesday, 20 November 2007 1:20 p.m. To: [EMAIL PROTECTED] Subject: Build Frustrations 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. I'm posting this to the straight-off questions list because I feel my other attempts have failed. Can someone sanity check me? I'm well aware of how to ask intelligent questions, to document what I have and have not done, of explaining WHY I have or have not done those things. I'm going to send it here, in the hopes maybe someone else has encountered this or might spot something I'm missing. If ANYONE can shed some light here, I'd appreciate it and am willing to compensate in some small way, if I can. Here's what I sent to the maintainers of the above two ports: Subject: apr versus apr-db42, as well as some other issues: Hello, First and foremost: I assume you're both reasonably busy professionals. That said, I believe there's either a bug in the core operating system here, or a bug in the way some of the critical ports are built, and I cannot figure it out alone. It is enough of a problem that it has confused at least one apache committer. That said, if you'd like to be compensated in some small way for your time, please point me to your amazon wishlists, paypal accounts, et cetera, and I'll try to do the right thing. I am mailing you because you are the maintainers of the apache-2.2.6 and apr ports. If there are other people I should be mailing, please let me know. 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. First, the basics: 1) Is it possible to get some documentation in either the short or long description as to what the difference between apr and apr-db42 is? 2) Also, is it at all possible to get some kind of documentation for the apr-svn port (if it still exists). 3) My big problem: (I'm going to post everything from here down to the apache-users mailing list, as well). 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. Because apr-db42 had been installed as part of a subversion requirement (not sure why), it caused my apache build to look in nonexistent places for libraries. %apr-1-config --apr-libtool /usr/local/build-1/libtool (the above path doesn't even exist) To fix this (and not break the svn port), I resorted to using --with-included-apr. The build THEN failed, claiming it could not find the installed expat libraries, in an error exactly like what this gentleman had: http://www.zulustips.com/2007/10/06/problems-compiling-apache-226-on-fre ebsd-62.html#more-54 And in fact, this apache developer had the same issue: http://www.mail-archive.com/[EMAIL PROTECTED]/msg18793.html (search the page for wtf) Like them, I had an installed expat, and had it listed in ldconfig -r (I also note there's a libexpat in /usr/src but don't know what it's there for). (I did not copy my errors because I thought I had found a solution, but it's the same error, I assure you). After that, I tried resorting to building apache with --with-expat=builtin I then got THIS error: /home/danm/httpd-2.2.6/srclib/apr/libtool --silent --mode=link gcc -g -O2 -o htpasswd htpasswd.lo -lm /home/danm/httpd-2.2.6/srclib/pcre/libpcre.la /home/danm/httpd-2.2.6/srclib/apr-util/libaprutil-1.la /home/danm/httpd-2.2.6/srclib/apr-util/xml/expat/lib/libexpat.la /home/danm/httpd-2.2.6/srclib/apr/libapr-1.la -lcrypt -lpthread /home/danm/httpd-2.2.6/srclib/apr-util/.libs/libaprutil-1.so: undefined reference to `libiconv_open' /home/danm/httpd-2.2.6/srclib/apr-util/.libs/libaprutil-1.so: undefined reference to `libiconv_close' /home/danm/httpd-2.2.6/srclib/apr-util/.libs/libaprutil-1.so: undefined reference to `libiconv' *** Error code 1 Stop in /home5/danm/httpd-2.2.6/support. *** Error code 1 Stop in /home5/danm/httpd
Re: Build Frustrations
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]
Re: Build Frustrations
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: prime# make PREFIX=/usr/local/apache2-fa WITH_MPM=worker === apache-worker-2.2.6_2 depends on file: /usr/local/bin/perl5.8.8 - found === apache-worker-2.2.6_2 depends on file: /usr/local/bin/autoconf-2.61 - not found ===Verifying install for /usr/local/bin/autoconf-2.61 in /usr/ports/devel/autoconf261 === Returning to build of apache-worker-2.2.6_2 === apache-worker-2.2.6_2 depends on file: /usr/local/bin/libtool - found === apache-worker-2.2.6_2 depends on shared library: expat.6 - found === apache-worker-2.2.6_2 depends on shared library: iconv.3 - found === Configuring for apache-worker-2.2.6_2 found apr source: srclib/apr found apr-util source: srclib/apr-util rebuilding srclib/apr/configure buildconf: checking installation... buildconf: autoconf not found. You need autoconf version 2.50 or newer installed to build APR from SVN. ./buildconf failed for apr *** Error code 1 Stop in /usr/ports/www/apache22. *** Error code 1 Stop in /usr/ports/www/apache22. prime# ls /var/db/pkg | grep auto autoconf-2.13.000227_5 autoconf-2.59_2 autoconf-2.61 autoconf-2.61_2 autoconf-wrapper-20071109 automake-1.10 automake-1.4.6_2 automake-1.9.6 -- If you need web space, give him a hard drive. If you need to do something really heavy, build him a computer. -Ilzarion, late friday night Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Build Frustrations
On Mon, 19 Nov 2007, Jerry McAllister wrote:
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.
Actually, I just tried this. This is not what I want. If I go to cd
/usr/ports/www/apache22, and do a make PREFIX=/some/other/directory, I do
NOT get the same thing I'd get building apache from source. I get ALL the
apache prerequisites installed under /some/other/dir, as opposed to the
apache standards places (for example config files which would normally be
in /usr/local/apache/conf now get installed in /some/other/directory/etc
(the port installs them in /usr/local/etc). As a bonus, dependent
packages get added to my package database under the same prefix, which
shouldn't happen. (i.e. I want ONLY the apache2.2 stuff in a
self-contained directory).
And the apache layout is hard coded (the only configure argument to be
so):
CONFIGURE_ARGS= --prefix=${PREFIX_RELDEST} \
--enable-layout=FreeBSD \
--with-perl=${PERL5} \
--with-port=${WITH_HTTP_PORT} \
--with-expat=${LOCALBASE} \
--with-iconv=${LOCALBASE} \
--enable-http
In short, not at all the same. Plus, doesn't solve the issue. I have all
the necessary binaries I need to build apache, it simply outright refuses
to build (and also, the APR version in ports is badly broken, nearly a
year old, and the APR maintainer can't even commit changes without making
a PR).
Also, this may seem silly as heck, but it should definitely be POSSIBLE to
build apache outside of the port (so, again, I feel use the port is not
the right answer...there's a deeper problem here).
I mean, obviously if they've got a standard layout defined in the apache
tree, the apache people expect the code to build on this OS (otherwise if
the ports-patches are so necessary, we would just define the layout there
too)
-Dan
--
This Is Not Goodbye!
-DM, August 11th 2001, 10 PMish Chicago Time
Dan Mahoney
Techie, Sysadmin, WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144 AIM: LarpGM
Site: http://www.gushi.org
---
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Build Frustrations
=== apache-worker-2.2.6_2 depends on file: /usr/local/bin/autoconf-2.61 - not found ===Verifying install for /usr/local/bin/autoconf-2.61 in /usr/ports/devel/autoconf261 === Returning to build of apache-worker-2.2.6_2 ... buildconf: checking installation... buildconf: autoconf not found. You need autoconf version 2.50 or newer installed to build APR from SVN. ./buildconf failed for apr These messages looks pretty similar I had after ports autotool cleanup (i.e. the new wrapper thingie). Solution for me was removing all the auto* ports and reinstalling only the new wrapper. APR working decent-like: [www] ~ httpd -V Server version: Apache/2.2.6 (FreeBSD) Server built: Oct 2 2007 00:21:11 Server's Module Magic Number: 20051115:5 Server loaded: APR 1.2.11, APR-Util 1.2.10 Compiled using: APR 1.2.11, APR-Util 1.2.10 ... -Reko ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Build Frustrations
--On November 19, 2007 11:00:44 PM -0500 Dan Mahoney, System Admin
[EMAIL PROTECTED] wrote:
On Mon, 19 Nov 2007, Jerry McAllister wrote:
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.
Actually, I just tried this. This is not what I want. If I go to cd
/usr/ports/www/apache22, and do a make PREFIX=/some/other/directory, I
do NOT get the same thing I'd get building apache from source. I get
ALL the apache prerequisites installed under /some/other/dir, as opposed
to the apache standards places (for example config files which would
normally be in /usr/local/apache/conf now get installed in
/some/other/directory/etc (the port installs them in /usr/local/etc).
As a bonus, dependent packages get added to my package database under
the same prefix, which shouldn't happen. (i.e. I want ONLY the
apache2.2 stuff in a self-contained directory).
Silly me. I had no idea there was a standard place for apache to put
its stuff. On *some* linux builds, the conf files are in
/etc/httpd/conf.d/ and the document root in /var/www. On FreeBSD they're
in /usr/local/etc/apache{ver.} and /usr/local/www/apache{ver},
respectively. What's the standard place I wonder? I suspect it has a
lot more to do with the conventions of the particular OS than it does with
the application.
And the apache layout is hard coded (the only configure argument to be
so):
CONFIGURE_ARGS= --prefix=${PREFIX_RELDEST} \
--enable-layout=FreeBSD \
--with-perl=${PERL5} \
--with-port=${WITH_HTTP_PORT} \
--with-expat=${LOCALBASE} \
--with-iconv=${LOCALBASE} \
--enable-http
In short, not at all the same. Plus, doesn't solve the issue. I have
all the necessary binaries I need to build apache, it simply outright
refuses to build (and also, the APR version in ports is badly broken,
Yet, oddly, I have it installed and it works fine.
httpd -V
Server version: Apache/2.2.6 (FreeBSD)
Server built: Oct 21 2007 00:03:07
Server's Module Magic Number: 20051115:5
Server loaded: APR 1.2.11, APR-Util 1.2.10
Compiled using: APR 1.2.11, APR-Util 1.2.10
Architecture: 32-bit
Server MPM: Prefork
threaded: no
forked: yes (variable process count)
Server compiled with
-D APACHE_MPM_DIR=server/mpm/prefork
-D APR_HAS_SENDFILE
-D APR_HAS_MMAP
-D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
-D APR_USE_FLOCK_SERIALIZE
-D APR_USE_PTHREAD_SERIALIZE
-D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
-D APR_HAS_OTHER_CHILD
-D AP_HAVE_RELIABLE_PIPED_LOGS
-D DYNAMIC_MODULE_LIMIT=128
-D HTTPD_ROOT=/usr/local
-D SUEXEC_BIN=/usr/local/bin/suexec
-D DEFAULT_PIDLOG=/var/run/httpd.pid
-D DEFAULT_SCOREBOARD=/var/run/apache_runtime_status
-D DEFAULT_LOCKFILE=/var/run/accept.lock
-D DEFAULT_ERRORLOG=/var/log/httpd-error.log
-D AP_TYPES_CONFIG_FILE=etc/apache22/mime.types
-D SERVER_CONFIG_FILE=etc/apache22/httpd.conf
nearly a year old, and the APR maintainer can't even commit changes
without making a PR).
And this is a bad thing because?
You *do* know that you can make any changes you want for your system? You
can edit the port any way you want or install from source without using
the port or, oh, whatever you like. It *is* unix, after all.
Also, this may seem silly as heck, but it should definitely be POSSIBLE
to build apache outside of the port (so, again, I feel use the port is
not the right answer...there's a deeper problem here).
Not silly at all. Some people build all their applications that way.
*But*, you have to know what you're doing.
I mean, obviously if they've got a standard layout defined in the apache
tree, the apache people expect the code to build on this OS (otherwise
if the ports-patches are so necessary, we would just define the layout
there too)
If I understood what you were saying here, I'd respond. You display all
the symptoms of a newbie to FreeBSD. You're used to seeing things in
certain places, and they're not there, and you're frustrated.
Try asking for help politely instead of insulting the very people who can
help you and denigrating the OS you're trying to build on.
You catch more flies with honey than vinegar.
Paul Schmehl ([EMAIL PROTECTED])
Senior Information Security Analyst
The University of Texas at Dallas
http://www.utdallas.edu/ir/security/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Build Frustrations
--On November 19, 2007 10:17:18 PM -0500 Dan Mahoney, System Admin [EMAIL PROTECTED] wrote: *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. I understand you may be frustrated right now, but really, this is a bit over the top. I just upgrade to apache2.2 and it runs just fine. I doubt seriously I'm the only person running it on FreeBSD. Using ports is no better. And again, I'll take anything anyone can offer to explain half this behavior: Easily explained prime# make PREFIX=/usr/local/apache2-fa WITH_MPM=worker === apache-worker-2.2.6_2 depends on file: /usr/local/bin/perl5.8.8 - found === apache-worker-2.2.6_2 depends on file: /usr/local/bin/autoconf-2.61 - not found ===Verifying install for /usr/local/bin/autoconf-2.61 in /usr/ports/devel/autoconf261 === Returning to build of apache-worker-2.2.6_2 === apache-worker-2.2.6_2 depends on file: /usr/local/bin/libtool - found === apache-worker-2.2.6_2 depends on shared library: expat.6 - found === apache-worker-2.2.6_2 depends on shared library: iconv.3 - found === Configuring for apache-worker-2.2.6_2 found apr source: srclib/apr found apr-util source: srclib/apr-util rebuilding srclib/apr/configure buildconf: checking installation... buildconf: autoconf not found. You need autoconf version 2.50 or newer installed to build APR from SVN. See this? It's telling you what's wrong. You need autoconf 2.50 or better. ./buildconf failed for apr *** Error code 1 Stop in /usr/ports/www/apache22. *** Error code 1 Stop in /usr/ports/www/apache22. prime# ls /var/db/pkg | grep auto autoconf-2.13.000227_5 autoconf-2.59_2 autoconf-2.61 autoconf-2.61_2 autoconf-wrapper-20071109 automake-1.10 automake-1.4.6_2 automake-1.9.6 ls /var/db/pkg/ | grep auto autoconf-2.61_2 autoconf-wrapper-20071109 automake-1.4.6_4 automake-wrapper-20071109 Notice a difference? Uninstall all the previous versions so your system isn't totally confused and fubared. Or run pkgdb -F and watch what happens. Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
