ipsure logo
Logo and Language
Login icon Language selection icon
Hello, guest
*NIX Active category menu left background Active category menu right background BACKUP Hands-On blog header image Right block of Hands-On blog header image Final menu block of Hands-On blog header image
MS TIP PKI PROJECTS WORDPRESS Türkçe HANDS-ON SERVICES IT BUSINESS CONTACT ABOUT REFERENCES TERMS RSS
Home page Hands-On Services IT Business Contact About References Terms of Use RSS

05/06/2010

Apache 2.2.15 Upgrade Failure: “checking for APR… configure: error: the –with-apr parameter is incorrect.”

Filed under: *NIX — Tags: , , , , , , — Sezgin Bayrak @ 14:32

There was an upgrade for apache22 (Apache/2.2.15) that added apr-ipv6-devrandom-gdbm-db42-1.4.2.1.3.9_1 Apache Portability Library package to the system by the straight attempt of portupgrade utility I executed without reading /usr/ports/UPDATING (20100518). Bad habit of not reading /usr/ports/UPDATING before performing the upgrade on my FreeBSD box ended up in;

Configuring Apache Portable Runtime library ...

checking for APR... configure: error: the --with-apr parameter is incorrect.
It must specify an install prefix, a build directory, or an apr-config file.
===> Script "configure" failed unexpectedly.
Please report the problem to apache@FreeBSD.org [maintainer] and attach the
"/usr/ports/www/apache22/work/httpd-2.2.15/config.log" including the output
of the failure of your make command. Also, it might be a good idea to provide
an overview of all packages installed on your system (e.g. an `ls /var/db/pkg`).
*** Error code 1

Stop in /usr/ports/www/apache22.
** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portinstall.54022.0 env make
** Fix the problem and try again.
** Listing the failed packages (-:ignored / *:skipped / !:failed)
! www/apache22 (configure error)

So I decided to glance at /usr/ports/UPDATING after struggling quite a while;

20100518:
 AFFECTS: users of devel/apr0, devel/apr1, www/apache20, www/apache22

 devel/apr port has been renamed to devel/apr1.

 WITH_APR_FROM_PORTS=yes for www/apache22 has been dissolved and may be
 removed from your configuration files; devel/apr1 is always used now.

 Please manually delete apache-2.\* if installed _before_ updating using
 either portmaster or portupgrade:

 pkg_delete -f apache-2.\*

 Then, if you use portmaster:

 portmaster -o devel/apr1 devel/apr

 If you use portupgrade:

 portupgrade -f -o devel/apr1 devel/apr

 Finally, reinstall Apache port if you deleted it earlier and update ports as
 usual (`XX' below is either 20 or 22):

 portinstall www/apacheXX

From that moment, uninstalling the apache package and issuing the “portupgrade -f -o devel/apr1 devel/apr” command and reinstalling apache consecutively wouldn’t work because forcing the upgrade of an already installed apr by specifying the origin somehow couldn’t be satisfying apache22.

In the end, uninstalling the apr1 itself solved my problem. Below is the sequence for those portupgraders who has no steady habit of investigating UPDATING file prior to upgrade processes. Of course if you didn’t break another thing when you boiled over apache.

# pkgdb -Fu
# portsclean -CD
# cd /usr/ports/www/apache22
# make deinstall clean
# portupgrade -f -o devel/apr1 devel/apr
# cd /usr/ports/devel/apr1
# make deinstall clean
# cd /usr/ports/www/apache22
# make install clean

This shall let apache bring apr1 by itself however it likes.

Related Posts with Thumbnails
Subscribe to our RSS feeds Email Subscription via FeedBurner RSS Subscription via FeedBurner
  1. php5-extensions-1.4 Upgrade Failure, php5-filter-5.3.2, php5-imap-5.3.2 and pcre issues: Stop in /usr/ports/security/php5-filter
  2. Configuring Apache, Installing PHP and PHP5-Extensions for Postfix Setup

7 Comments »

Trackbacks

Reader Comments

Eric05/06/2010 21:28

Damn, thanks for this. I really should read UPGRADING more often too :\

asceta10/06/2010 09:35

Hi,

I’m also the one who didn’t care about /usr/ports/UPDATING – just put some scripts in crone to actualize ports db with fetching some files, and from time to time- portupgrade -ayrR…

yeah, then I went to the situation with boiled apache :). Automatization not always is good.

Thanks for your tips!

Skye04/08/2010 11:12

Thanks, this bit me too.

mark18/08/2010 20:29

Am indebted to your sleuthing and, more importantly, to taking the time to blog about it. Meet me at the pub and I’ll buy the beer.

George18/01/2011 00:12

Did all steps without first (ports db was already fresh) and apache updated fine. Thanks a lot!

p.s. need to read updating info first

cj21/04/2011 23:37

Thanks for the guide! You saved my day.

RSS feed for comments RSS feed for comments on this post. TrackBack URL

Leave a comment