=dev-lang/php-5.4.8 with use flags: apache2 gd -ldap mysql mysqli curl soap, thought without last three flags it compiles. I attach config.log file, which is refered in the following emerge output: configure: error: There is something wrong. Please check config.log for more information. !!! Please attach the following file when seeking support: !!! /dane/portage/tmp/portage/dev-lang/php-5.4.8/work/sapis-build/cli/config.log * ERROR: dev-lang/php-5.4.8 failed (configure phase): * econf failed I also attach the whole build.log where are all the use flags. Reproducible: Always Steps to Reproduce: 1. add mysqli curl soap to use flags for dev-lang/php-5.4.8 2. emerge =dev-lang/php-5.4.8 Actual Results: Fails in configure phase. Expected Results: Compiles and installs.
Created attachment 335494 [details] emerge info file
...so, where's that config.log ?
Created attachment 335538 [details] config.log
Please attach the build.log.
(In reply to comment #4) > Please attach the build.log. No point of a build log. Either it's a revdep-rebuild case or something a bit more complicated but still related to openldap rebuild (on either openldap or cyrus-sasl side). That suggests that if this is a genuine bug, it's assigned wrong.
(In reply to comment #5) > (In reply to comment #4) > > Please attach the build.log. > > No point of a build log. Exactly, it contains no more information than we already need and have. > Either it's a revdep-rebuild case or something a bit more complicated but > still related to openldap rebuild (on either openldap or cyrus-sasl side). Maybe, but since the reporter has USE="-ldap" so he doesn't want to use those. There is the other case where he might have curl with USE="ldap" and openldap with USE="sasl", in which case these are pulled in indirectly through USE="curl" and a revdep-rebuild might help. If there then were still a bug with openldap, I would assume curl to fail as a result... > That suggests that if this is a genuine bug, it's assigned wrong. I wouldn't be so sure of that. What is interesting is that it introduces -lldap in this config.log while there was no --with-ldap parameter passed to configure; note that we're in an USE="-ldap" case. Also, since there is no way to specify not to use ldap ; it feels like if ./configure doesn't respect the Gentoo way of doing things. What's also clear, but perhaps irrelevant, is that USE="curl" introduces the failing check.
... ... ... The failed link line had following libs '-lcurl -lssl -lcrypto -lldap -lrt -lz -lbz2 -lpcre -lm -ldl -lnsl -lxml2 -lm'. The error indicated not a missing lib, but missing symbols in libldap. The most likely reason for that is an incorrect openldap build. The question is just whether it's a user specific problem or if it's something reproducable. One way or the other, it doesn't look like anything that could or should be fixed on php side. Anyway, the line that added '-lldap' seems to be the check for curl. IIRC, php still uses curl-config to get the libs instead of pkg-config, which tends to pollute the var with such noise like '-lldap'. Still, if libldap was built correctly, this bug wouldn't happen.
Is this bug still around?
I cannot confirm, since that laptop has crashed and since then I have moved to a new computer.
(In reply to comment #9) > I cannot confirm, since that laptop has crashed and since then I have moved > to a new computer. Okay. Closing for now then. Reopen if the issue resurfaces.
