Bug 151680

Summary:	www/eaccelerator Makefile glitch
Product:	Ports & Packages	Reporter:	Michael Ross <michael.ross>
Component:	Individual Port(s)	Assignee:	Alex Dupre <ale>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	Latest
Hardware:	Any
OS:	Any

Description Michael Ross 2010-10-24 11:00:21 UTC

eAccelerator compiles, 
but fails to start with:
"eAccelerator: shmmax should be at least 2MB",
regardless of shmmax sysctl value/shmmax config value.

Fix: 

Change in Makefile:

CONFIGURE_ARGS= --enable-eaccelerator=shared\

to

CONFIGURE_ARGS= --with-eaccelerator-shared-memory\

as per http://www.eaccelerator.net/wiki/CompileConfiguration
fixes this error.

Comment 1 Mark Linimon freebsd_committer

2010-10-24 12:17:58 UTC

Responsible Changed
From-To: freebsd-ports-bugs->ale

Fix synopsis and assign.

Comment 2 Alex Dupre freebsd_committer

2010-10-25 10:04:01 UTC

State Changed
From-To: open->closed

Bogus, doesn't exist that configure option.

Comment 3 michael 2010-10-25 11:00:46 UTC

Closed:	"Bogus, doesn't exist that configure option." ?

Sorry, But

<quote http://www.eaccelerator.net/wiki/CompileConfiguration>

--with-eaccelerator-shared-memory

Include eaccelerator shared memory functions. The name is a bit confusing,  
but this will include the eaccelerator_get, _put, ... functions that allow  
scripts to store data in the eAccelelerator cache. This options has been  
enabled by default until version 0.9.5. When enabling this feature on  
systems where you can't trust all users, like in shared hosting  
environments, this could really fill up the cache causing all scripts to  
only exist on disk which isn't good for performance.

</unquote>

Seems to exist alright...

I did the following:

-> compile eaccelerator from ports & install
-> Won't run becaues of "eAccelerator: shmmax should be at least 2MB"
-> checked that shmmax is actually >2MB
-> dug through the web
-> deinstalled, changed Makefile as in bug report
-> make clean, make install
-> Runs as per Spec/Doc/Whatever.

This non-existing configure option sure fixed my problem.