Neil Bothwick <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Tue, 17 Oct 2006 08:47:23 +0100:
> On Mon, 16 Oct 2006 23:33:06 -0700 (PDT), Steve Herber wrote: > >> configure: error: There is something wrong. Please check config.log for >> more information. >> >> !!! ERROR: dev-lang/php-5.1.6-r6 failed. > >> Some of my major packages get this error and I wonder what causes it? >> I am not interested in a solution for php, but a guideline to help me >> fix any package with this problem. > > The lines before the error should give some clues. The config.log it > mentions can be found in $PORT_TMPDIR/dev-lang/php-5.1.6/work in this > instance, that should give a more detailed error message. > > This isn't necessarily a single problem for all the affected packages; the > configure script carries out a large number of tests, any one of which > could have failed. Additionally, note that with some tests, any warnings (even if they are harmless) can cause the test to fail. A common example would be unsupported CFLAGS -- CFLAGS that your currently configured version of GCC doesn't recognize and so ignores, but spits a warning about. Maybe you setup your CFLAGS with a different version of GCC that recognized different flags, or whatever you followed suggesting those CFLAGS was based on a different GCC version. Particularly if whatever they are testing is only a gcc-warning as well, guess what, they usually fail on any warning. As it happens, the Gentoo/amd64 arch team had enough problems reported due to this that they instituted a filter in their profiles that removes most flags the currently configured version of gcc doesn't recognize, so the problem happens less frequently than it did, but the unrecognized CFLAG warning isn't the only one gcc has by far, and if one of the others pops up in a test, it could trigger a test failure and ultimately a configure error as well. In ordered to properly troubleshoot the general problem (a configure error as reported in config.log), one really needs to know bash (well sh, which on Gentoo is normally bash) scripting, since that's what the configure script is written in. The config.log file references line numbers in the actual configure script, and if it's not immediately apparent from config.log what the problem is, the next step is to open the configure script to that line and figure out what it's doing, duplicating the process by hand or adding echo debugs to the configure script where necessary to see what's going on. With a decent grasp of bash and at least a vague idea of what all those tests in the configure script are all about (note, knowing C/C++ is generally NOT necessary), one can usually figure out what's going on and why, either correcting the problem (such as CFLAGS that are choking the test in question) or bugging either with Gentoo or very occasionally upstream, as appropriate. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- [email protected] mailing list
