[MacPorts] #24605: P5-cgi-speedycgi +apple_apache :: latest version :: Runtime error -
MacPorts
noreply at macports.org
Thu Apr 22 15:39:58 PDT 2010
#24605: P5-cgi-speedycgi +apple_apache :: latest version :: Runtime error -
----------------------------------------------------------------+-----------
Reporter: phiwie@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: High | Milestone:
Component: ports | Version: 1.8.2
Keywords: speedycgi, CGI, speedy, +apple_apache, perl, perl5 | Port: p5-cgi-speedycgi
----------------------------------------------------------------+-----------
I had SpeedyCGI installing and running successfully on Mac OS X 10.4 and
10.5 (after some hacking). However, now I experience problems after
recently clean-installing 10.6.3 with Apple Apache 2.2.14 and Perl 5.10.0
and setting-up a completely fresh Mac Ports system (BerkeleyDB 4.7
installed by myself).
First problem (solved): p5-cgi-speedycgi +apple_apache aborts installation
complaining about the missing perl5 port, even if Apple Perl is there.
Second problem (solved): p5-cgi-speedycgi +apple_apache still ships with
the bug that keeps it from installing. In src/speedy_backend_main.h:
-#define speedy_new(s,n,t) New(123,s,n,t)
+#define speedy_new(s,n,t) Newx(s,n,t)
Third problem (not solved): after successful compiling via port install p5
-cgi-speedycgi +apple_apache, and after copying
/opt/local/share/doc/speedycgi/mod_speedycgi.so to /usr/libexec/apache2/,
I get a server error when initiating SpeedyCGI. Apple Apache running in
64bit mode on a Mac Pro Intel Dual 2.8GHz Harpertown. Here is an excerpt
of the crash report:
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000007
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0xffffffff ebx: 0x00064e1a ecx: 0x00000000 edx: 0xffffffff
edi: 0x00009edb esi: 0x00800000 ebp: 0xbfffe468 esp: 0xbfffe3d0
ss: 0x0000001f efl: 0x00010286 eip: 0x00064e29 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x00000007
I would be greatful in learning soon what the cause could be, thanks!
--
Ticket URL: <http://trac.macports.org/ticket/24605>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list