apache2 2.2.6_0 (2.2.8_0) build failure: unable to infer tagged configuration

[jerry.jalava@…]

Is it just my machine or is there something wrong with the script in Apache 2.2.6 port? This is what I get when trying to upgrade:

-------->  Building apache2 with target all
Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6" && make all " returned error 2
Command output: Making all in srclib
Making all in os
Making all in unix
/opt/local/share/apr-1/build/libtool --silent --mode=compile /usr/bin/gcc-4.0 -I/opt/local/include  -O2  -DDARWIN -DSIGPROCMASK_SETS_THREAD_MASK -no-cpp-precomp  -I/opt/local/include  -I. -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/os/unix -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/server/mpm/prefork -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/http -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/filters -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/proxy -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/include -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/generators -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/mappers -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/database -I/opt/local/include/apr-1 -I/opt/local/include -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/server -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/proxy/../generators -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/ssl -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/dav/main  -prefer-non-pic -static -c unixd.c && touch unixd.lo
libtool: compile: unable to infer tagged configuration
libtool: compile: specify a tag with `--tag'
make[3]: *** [unixd.lo] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1

Error: Unable to upgrade port: 1
------

[ryandesign@…]

Never seen such a problem. apache2 2.2.6_0 works fine for me on Mac OS X 10.4.11 Intel with Xcode 2.4.1 and MacPorts compiled from trunk. You should tell us your version of Mac OS X, Xcode and MacPorts, and what architecture your processor is. You should also try "sudo port selfupdate" followed by "sudo port clean --work apache2" and "sudo port install apache2" and see if it works then. Assigning ticket to port's maintainer.

[ryandesign@…]

Interesting, the same error message was reported for the mjpegtools port in #13648.

[christian@…]

Also seeing this on OS X 10.5.1 with XCode 3.0 and MacPorts 1.600. Did both sudo port selfupdate, sudo port clean --work apache2 and sudo port install apache2. How may I provide more debugging information?

[josh-macports@…]

I'm seeing this too. MacPorts 1.60, XCode 3.0, OS 10.5.1, x86. I'm attaching a full debug-mode build log.

[ryandesign@…]

Has duplicate #13775.

[juno@…]

work around

[jwa@…]

This applies to 2.2.8, too. Seems to go further, if one patches configure in addition to/instead of configure.in.

[jwa@…]

configure patch

[jwa@…]

Well, my environment in which apache2 2.2.8 doesn't initially build before the patched configure, is OS X 10.4.11 with Xcode 2.5. I also add myself to cc: list to get notifications about updates.

[dbraband@…]

How do i apply these patches?

Thanks for your help.

[jwa@…]

I'll attach my Portfile diff. Patch your's with that (or edit Portfile), add the patchfiles in subdirectory 'files' in apache2 port directory.

[jwa@…]

Portfile diff with patch files for configure

[dbraband@…]

It worked. Thank you!

[ryandesign@…]

No patch to the apache2 portfile should be necessary. There has been a long discussion on macports-users in which it seems the problem is that apr was installed with MacPorts < 1.6.0 and now users are trying to install apache2 with MacPorts >= 1.6.0. MacPorts 1.6.0 changed the name of the compiler from "gcc" to "/usr/bin/gcc-4.0" and even though these are the same compiler, the libtool in apr doesn't know this, and complains. The solution is to rebuild apr with MacPorts 1.6.0. Daniel, I'm reassigning this to you since apr is your port. I see the current apr portfile 1.2.12 was last modified 2007-12-04 and MacPorts 1.6.0 was released 2007-12-16 so it's entirely possible that someone built apr 1.2.12 with MacPorts < 1.6.0. I believe the solution is to simply bump the revision number of the apr portfile by one, making no other changes, to force everyone to rebuild it so that we know it was built with MacPorts >= 1.6.0.

[dluke@…]

apr's revision bumped in r33741

[ryandesign@…]

Thanks. And in case anyone was wondering, apr0 should not be affected since its version was already bumped on 2008-01-12.

[ryandesign@…]

Has duplicate #14145.