php-5.0.2 and mod_php-5.0.2 work excellent on amd64, please add keyword, because after resyncing emerge always wants to downgrade Reproducible: Always Steps to Reproduce: 1. 2. 3.
Confirmed. mod_php and php 5.0.2 work fine on my amd64 machine. Unfortunately, the were not keyworded for amd64. Please add at least "-amd64", but imho it should also be safe to add "~amd64"
I can confirm both, dev-php/php-5.0.2-r1 dev-php/mod_php-5.0.2 Works for me. ~amd64 had to be added to the ebuild. Made a copy to my overlay dir, to prevent portage wanting to downgrade after syncing
in cvs. thanks
The keyword was removed again! I don't know why you did this, but could you please add at least "-amd64" or "-*"? php works excellent on my amd64 and movind every new php ebuild into my overlay dir just to add a keyword so portage won't refuse it seems like overkill for this purpose.
PHP 5 was removed because imap support(USE=imap) doesn't yet work on amd64. Seeing as how I didn't have imap in my keywords, I missed this when commiting. If you're able to run php5 with imap support, please let us know what you needed to do to get it working(if anything).
Please also take a look at http://bugs.gentoo.org/show_bug.cgi?id=61392 My system runs with "Portage 2.0.51_rc9 (default-linux/amd64/gcc34-2004.2, gcc-3.4.2, glibc-2.3.4.20041006-r0, 2.6.9-rc3 x86_64)" and there it is no problem to build php5* with imap. I had the same problems (also with e.g. mtr) with a glibc compiled with gcc 3.3! Please remember that gcc 3.3.4 does not fully support amd64. Regards Jens
