[MacPorts] #20589: p5-cgi-speedycgi fails on 10.5 server
MacPorts
noreply at macports.org
Tue Jun 28 19:11:10 PDT 2011
#20589: p5-cgi-speedycgi fails on 10.5 server
-------------------------------------+--------------------------------------
Reporter: schneider.pj@… | Owner: markd@…
Type: defect | Status: reopened
Priority: Normal | Milestone:
Component: ports | Version: 1.7.1
Resolution: | Keywords:
Port: smokeping |
-------------------------------------+--------------------------------------
Comment(by filter@…):
The error did not occur when installing on 10.6 using Apple's built in
version of apache2. The error did occur when performing an identical
installation on 10.5 also using Apple's built in version of apache2. So,
it would seem that p5-cgi-speedycgi still does work, as it installed and
runs without a hitch over buit in apache2 on my 10.6 system:
$ httpd -v
Server version: Apache/2.2.17 (Unix)
$ ps -ax | grep speedy
3387 ?? 0:00.40 /opt/local/bin/speedy_backend
/opt/local/var/smokeping/smokeping.cgi
3390 ?? 0:48.40 /opt/local/bin/speedy_backend
/opt/local/var/smokeping/smokeping.cgi
Yet, I still can't get it to run on 10.5:
$ httpd -v
Server version: Apache/2.2.14 (Unix)
$ sudo apachectl -k restart
httpd: Syntax error on line 116 of /private/etc/apache2/httpd.conf: Cannot
load /usr/libexec/apache2/mod_speedycgi.so into server:
dlopen(/usr/libexec/apache2/mod_speedycgi.so, 10): no suitable image
found. Did find:\n\t/usr/libexec/apache2/mod_speedycgi.so: mach-o, but
wrong architecture
I am comfortable with installing macports apache and with having both
versions installed, but just prefer to use built in version when possible.
It clearly can work, as I've got it to do so on the 10.6 host without a
problem. According to your note, it would seem that this is a miracle, as
p5-cgi-speedycgi shouldn't be able to work at all. Is there a way that I
can figure out how and why it is managing to work on the 10.6 machine? I
am sure that it is using the built in version of apache. The configuration
file for the built in version is the only one that has LoadModule
speedycgi_module modules/mod_speedycgi.so enabled, and shutting down the
server from the Sharing control panel shuts down the smokeping site.
Regarding the apple_apache option, I think it's optimal to give users as
much choice as possible -- a user may already have a fairly sophisticated
and/or in-production configuration of Apple's apache already set up when
electing to install smokeping. I personally appreciated discovering that
the apple_apache option existed. Thanks!
--
Ticket URL: <https://trac.macports.org/ticket/20589#comment:15>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list