Opened 16 years ago

Last modified 9 years ago

#16583 new defect

php5-eaccelerator 0.9.5.3 fails during configure - need to pass user id for sysvipc

Reported by: moody@… Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: ports Version: 1.6.0
Keywords: Cc: smbmacportstrac@…
Port: php5-eaccelerator

Description (last modified by ryandesign (Ryan Carsten Schmidt))

# port --version
MacPorts 1.600

# php --version
PHP 5.2.6 (cli) (built: Jul 17 2008 23:04:49) 
Copyright (c) 1997-2008 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2008 Zend Technologies

# port install php5-eaccelerator +sessions +content_caching
--->  Fetching php5-eaccelerator
--->  Attempting to fetch eaccelerator-0.9.5.3.tar.bz2 from http://bart.eaccelerator.net/source/0.9.5.3/
--->  Verifying checksum(s) for php5-eaccelerator
--->  Extracting php5-eaccelerator
--->  Configuring php5-eaccelerator
Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_php5-eaccelerator/work/eaccelerator-0.9.5.3" && ./configure --prefix=/opt/local --with-php-config=/opt/local/bin/php-config --with-eaccelerator-sessions --with-eaccelerator-content-caching " returned error 1
Command output: checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for unistd.h... (cached) yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking sched.h usability... yes
checking sched.h presence... yes
checking for sched.h... yes
checking mandatory system headers... no
checking whether union semun is defined in sys/sem.h... yes
checking for sysvipc shared memory support... no
checking for mmap shared memory support... yes
checking for mmap on /dev/zero shared memory support... no
checking for anonymous mmap shared memory support... yes
checking for posix mmap shared memory support... yes
checking for best shared memory type... anonymous mmap
checking for spinlock semaphores support... no
checking for pthread semaphores support... no
checking for posix semaphores support... yes
checking for sysvipc semaphores support... yes
checking for fcntl semaphores support... yes
checking for flock semaphores support... yes
checking for best semaphores type... configure: error: "You need to pass the user id eaccelerator will be running under when using sysvipc semaphores"

Attachments (1)

main.log (8.1 KB) - added by erik@… 11 years ago.
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_php_php5-eaccelerator/php5-eaccelerator/main.log

Download all attachments as: .zip

Change History (24)

comment:1 Changed 16 years ago by mf2k (Frank Schima)

Keywords: php5-eaccelerator removed
Owner: changed from macports-tickets@… to alakazam@…

Assigning to maintainer.

comment:2 Changed 16 years ago by alakazam@…

Could you specify your version of Mac OS, as well as the output from port installed php5 ? Thanks !

(The following is for my future (~2 days) exploration of this issue, or for other people trying to fix it)

This eAccelerator is probably related :

http://eaccelerator.net/ticket/18

This changeset is also related :

http://eaccelerator.net/changeset/150

comment:3 in reply to:  2 Changed 16 years ago by moody@…

Replying to alakazam@…:

Could you specify your version of Mac OS

Mac OS 10.5.5 - I've seen this on two machines:

Darwin pearl.isi.edu 9.5.0 Darwin Kernel Version 9.5.0: Wed Sep 3 11:31:44 PDT 2008; root:xnu-1228.7.58~1/RELEASE_PPC Power Macintosh

Darwin peugeot.local 9.5.0 Darwin Kernel Version 9.5.0: Wed Sep 3 11:29:43 PDT 2008; root:xnu-1228.7.58~1/RELEASE_I386 i386

as well as the output from port installed php5 ?

# port installed php5
The following ports are currently installed:
  php5 @5.2.6_1+apache2+fastcgi+macosx+mysql5+pear+pspell+readline+sockets+t1lib (active)

(The following is for my future (~2 days) exploration of this issue, or for other people trying to fix it)

This eAccelerator is probably related :

http://eaccelerator.net/ticket/18

This changeset is also related :

http://eaccelerator.net/changeset/150

Last edited 12 years ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)

comment:4 Changed 16 years ago by moody@…

I added the following to the Port file:

configure.args-append --with-eaccelerator-userid=_www

and the installation was successful

Last edited 12 years ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)

comment:5 Changed 16 years ago by alakazam@…

I have just checked the output of my configuration script ; it would seem that I have support for "spinlock semaphores", and that they are chosen as being the best semaphore type. I think adding a dependency towards spinlock semaphore support would be a more reliable fix.

comment:6 Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)

Description: modified (diff)

comment:7 Changed 15 years ago by (none)

Milestone: Port Bugs

Milestone Port Bugs deleted

comment:8 Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added

Is this still an issue with php5 @5.3.0_2 and php5-eaccelerator @0.9.6-rc1_0?

comment:9 Changed 15 years ago by alakazam@…

Owner: changed from alakazam@… to alakazam@…
Status: newassigned

comment:10 Changed 15 years ago by alakazam@…

Resolution: worksforme
Status: assignedclosed

comment:11 in reply to:  description Changed 15 years ago by smbmacportstrac@…

configure: error: "You need to pass the user id eaccelerator will be running under when using sysvipc semaphores"

This is still a problem with the latest macports on 10.5.7!

As "moody@" said, this fixes the problem:

configure.args-append --with-eaccelerator-userid=_www
Last edited 12 years ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)

comment:12 Changed 15 years ago by smbmacportstrac@…

Cc: smbmacportstrac@… added

Cc Me!

comment:13 in reply to:  10 Changed 14 years ago by smbmacportstrac@…

Resolution: worksforme
Status: closedreopened

This problem still exists on MacOS X 10.5.8 PPC with php5-eaccelerator @0.9.6 and the latest macports. As has been noted for 22 months, the fix is to include this line in the Portfile: configure.args-append --with-eaccelerator-userid=_www

alakazam insists it "worksforme", making this a bit frustrating since I've had to deal with this for quite a while now on 2 ppc machines. alakazam, were you using 10.6 at the time you confirmed that it was working for you? If that is indeed the difference, is there a way to conditionalize the configure arguments for 10.5 vs 10.6?

comment:14 Changed 14 years ago by alakazam@…

Patches are obviously welcome, and I probably didn't test on mac os 10.5. The lack of response when I was looking into the bug probably made me close it.

I think adding a darwin_X variant with X corresponding to the right mac os version should work — not sure what the recommended means of os-version targeting is.

comment:15 in reply to:  14 Changed 14 years ago by danielluke (Daniel J. Luke)

Replying to alakazam@…:

I think adding a darwin_X variant with X corresponding to the right mac os version should work — not sure what the recommended means of os-version targeting is.

A platform variant is what you want.

see http://guide.macports.org/#reference.variants.platform

comment:16 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

I'm just not sure why a platform variant would be needed; Don't see why --with-eaccelerator-userid shouldn't just be used always. I'll see if I can do some testing.

comment:17 Changed 13 years ago by alakazam@…

Owner: alakazam@… deleted
Status: reopenednew

comment:18 in reply to:  16 Changed 13 years ago by smbmacportstrac@…

Ping. This problem still exists on MacOS X 10.5.8 PPC with php5-eaccelerator @0.9.6.1 and the latest macports (2.0.1). As has been noted for 3 years, the fix is to include this line in the Portfile: configure.args-append --with-eaccelerator-userid=_www.

comment:19 Changed 12 years ago by smbmacportstrac@…

Ping timeout. Ping. This problem still exists on MacOS X 10.5.8 PPC with php5-eaccelerator @0.9.6.1 and the latest macports (2.0.1). As has been noted for 4 years, the fix is to include this line in the Portfile: configure.args-append --with-eaccelerator-userid=_www.

comment:20 Changed 12 years ago by mf2k (Frank Schima)

Cc: ryandesign@… removed
Keywords: sysvipc removed
Owner: set to ryandesign@…

It looks like the maintainer isn't on macports anymore and the ticket got assigned to nobody.

Changed 11 years ago by erik@…

Attachment: main.log added

/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_php_php5-eaccelerator/php5-eaccelerator/main.log

comment:21 Changed 11 years ago by erik@…

This problem still exists on Mac OS X 10.5.8 Intel with php5-eaccelerator @0.9.6.1_13 and the latest macports (2.0.3).

comment:22 Changed 10 years ago by erik@…

This problem still exists on Mac OS X 10.5.8 Intel with php5-eaccelerator @0.9.6.1_17+universal and the latest version of MacPorts (2.2.1)

I made it work by manually adding the fix first mentioned by moody@…: In the Portfile found here:

/opt/local/var/macports/sources/rsync.macports.org/release/ports/php/php5-eaccelerator/Portfile

I inserted the following after line 34:

configure.args-append --with-eaccelerator-userid=_www

I then ran the rest manually (I actually have nearly no clue about this...!):

port clean php5-eaccelerator
port configure php5-eaccelerator
port build php5-eaccelerator
port test php5-eaccelerator (turns out there are no tests defined in this port...)
port destroot php5-eaccelerator
port install php5-eaccelerator
port activate php5-eaccelerator @0.9.6.1_17+universal

I worked for me, although there is probably a better way. I don't know how to create a patch file to submit, sorry.

comment:23 Changed 9 years ago by jmroot (Joshua Root)

Just noting that this port has been replaced with php53-eaccelerator. Does the problem still exist there?

Note: See TracTickets for help on using tickets.