#13653: apache2 2.2.6_0 (2.2.8_0) build failure: unable to infer tagged configuration -------------------------------------+-------------------------------------- Reporter: jerry.jalava@gmail.com | Owner: dluke@macports.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.5.2 Resolution: | Keywords: -------------------------------------+-------------------------------------- Changes (by ryandesign@macports.org): * cc: imajes@macports.org (added) * owner: imajes@macports.org => dluke@macports.org Comment: No patch to the apache2 portfile should be necessary. There has been a [http://lists.macosforge.org/pipermail/macports- users/2008-February/008671.html 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. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/13653#comment:14> MacPorts </projects/macports> Ports system for Mac OS