Date: Thu, 16 Jun 2011 10:52:46 -0400 From: Michael Powell <nightrecon@hotmail.com> To: freebsd-questions@freebsd.org Subject: Re: Another PHP5 problem Message-ID: <itd5ap$nm1$1@dough.gmane.org> References: <64D6EF8B-A799-4D8C-A688-FC020CCFEFD1@d3photography.com> <3.0.1.32.20110615175738.019581f8@sage-american.com> <3.0.1.32.20110615155910.019581f8@sage-american.com> <3.0.1.32.20110615150619.019581f8@sage-american.com> <3.0.1.32.20110615090401.0181fea8@sage-american.com> <3.0.1.32.20110615090401.0181fea8@sage-american.com> <3.0.1.32.20110615150619.019581f8@sage-american.com> <3.0.1.32.20110615155910.019581f8@sage-american.com> <3.0.1.32.20110615175738.019581f8@sage-american.com> <3.0.1.32.20110615191858.018e54e0@sage-american.com> <64D6EF8B-A799-4D8C-A688-FC020CCFEFD1@d3photography.com> <85B7376289F04B2596EBE3090DB9D970@rivendell> <3.0.1.32.20110616085819.018c54e0@sage-american.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jack L. Stone wrote: [snip] > > Now, I wrestling with the apache2 and apr0 issue. The apache port Makefile > wants apr0, but it now has vulnablilities. Ports UPDATING says to do this > with apr: > - remove apache2 and then: portupgrade -f -o devel/apr1 devel/apr > ...and then reinstall apache2. That didn't work because the Makefile in > apache still wants apr0. I changed the Makefile to apr1 but the build > failed after it looked again for that apr0 later in the build. I didn't > find another call for apr0. > > What have others done for this? This is about the last issue I know about > after the major upgrade of the ports. > > Thanks for all the help so far -- just any other help on the apr thingy > would be nice. Yes, I have googled and always do before going to the > trough here. > I seem to remember vaguely going through this once upon a time, I believe it was circa trying to move from apache 1.3.xx to apache 2.0. apr0 was for 1.3 and apr1 was for apache 2.0. I seem to recall a chicken and egg scenario about installing the apr(x) port first, then during the apache install it tried to install it again. Back then the apache 2.0 would mistakenly go looking for apr0 the second time unless there was something like a USE_APACHE= 20 (or something like that) in make.conf. I remember chasing my tail on that one. I think later the USE_APACHE= 20 became deprecated and APACHE_PORT=www/apache22 replaced it. Really, apache2 is dated. Apache22 is now the default. You would only require the make.conf entries described above to force a change from default(22). It doesn't have the problems you're having. If you are at this stage you should really make the move to apache22. Be advised though, it pulls in a few more dependencies than I'd really like, especially the apr1 (now named apr-ipv6-devrandom-gdbm-db42-1.4.5.1.3.12) port installing Python27. You might have to make a couple of twiddles on .conf files but it is something easy to do. But the sticky point is the apr-ipv6-devrandom-gdbm-db42-1.4.5.1.3.12 is the new apr1 port for apache22 installs, not the old devel/apr(x) - those are for 1.3 and 2.0 and will need the make.conf entry (22 won't need anything). At any rate take a gander at /usr/ports/Mk/bsd.apache.mk for more info. But if it were me instead of fighting I'd just go with the apache22 default instead of struggling with apache20. -Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?itd5ap$nm1$1>