Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 332257 - dev-lang/php-5.2.14: fastcgi not working
Summary: dev-lang/php-5.2.14: fastcgi not working
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal
Assignee: PHP Bugs
URL:
Whiteboard:
Keywords:
: 332337 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-08-11 14:33 UTC by Markus Passerschröer
Modified: 2010-08-12 08:36 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Passerschröer 2010-08-11 14:33:28 UTC 
The force-cgi-redirect and discard-path USE flags have been removed from the ebuild. I get the following errors when trying to run PHP scripts with FastCGI and PHP 5.2.14:

> Connection reset by peer: mod_fcgid: error reading data from FastCGI server
Comment 1 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2010-08-11 17:19:56 UTC 
seeing the same, the upgrade to 5.2.14 was not smooth, I reverted to .13 to continue running my site.
Comment 2 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2010-08-11 17:52:05 UTC 
The problem is, regardless of USE=cgi setting, --disable-cgi is still passed to configure. I worked around this issue by running:

"EXTRA_ECONF="--enable-cgi --enable-fastcgi" emerge -av1 php"

it was kinda a wild guess on my part based on looking at the logs and whatnot.
Comment 3 Matti Bickel (RETIRED) gentoo-dev 2010-08-11 20:57:21 UTC 
Crap. In fact, src_configure now fails to pass --enable-fastcgi. Normal cgi
should still be working.

I fixed this and readded the two missing USE flags. I'll also set up some
containers to have a test env per SAPI this week, so this won't show up again.
Thanks for noticing!
Comment 4 Eray Aslan gentoo-dev 2010-08-12 08:36:32 UTC 
*** Bug 332337 has been marked as a duplicate of this bug. ***