It's needed to include this in the src_compile() section of ebuild to work correctly (I suppouse that mysql support will be enabled by default in PHP configuration stage): use mysql || myconf="${myconf} --without-mysql"
Yes, it will automatically enabled, but shouldn't break the php build process. I'll add it to the next ebuild version from me. Roman
I think that only happens when mysql isn't emerged and the correspondig libraries are missing from system. How the mysql support it's enabled by default tries to compile/link the mysql module that breaks php emerge
i agree with Xavier on this one ... make sure mysql has been emerged ... mine did not compile until i emerged mysql. however, for those people who do not want to emerge mysql (and thus dont want mysql support in php), there should be a line in the ebuild to enable --without- mysql my fix: use mysql && myconf="${myconf} --with-mysql=/usr" ! use mysql && myconf="${myconf} --without-mysql" this disables mysql when ppl dont want it and enable mysql when they do ... if you always pass the --without-mysql flag, php will compile its own mysql module. however, their mysql module is not the latest and greatest, it is a generic solution. the reason they link with the mysql libraries is so that they can build an optimized mysql module that takes advantage of the latest features
Fixed in #2820
