At 12:40 PM 3/5/02 +0300, you wrote: >pp wrote: > >>>There is a problem concerning PHP extension (ver 1.4.2). >>>MKALL makes file named midgard.a that php can't use, >>>instead of midgard.so. What can I do about it? >>>php ver 4.0.6 >>Would You give some output? >>Do You have php4-dev (devel) ? > >Output seems like to be similar to usual compilation process. >There is php4 installed as shared module via apxs from source. >System is FreeBSD. The most wondering thing is that 3 weeks >ago extension was compiled w/o any problem on the same system. >Two things were changed - libmidard was recompiled w/SG support >and PHP module was recompiled w/curl support.
[directed towards original poster...] When you build the PHP module, is the command 'phpize' executed? Is the execution of the phpize script successful? The command 'phpize' is included with the source and with PHP-devel rpms and lets you compile a PHP dynamically-loaded extension without rebuilding the entire PHP source tree. What I've found is that even if you take the sample PHP extension created by the ext_skel script in the PHP tarball, it won't build the .so file unless you either build using the source tree and take a couple extra steps as documented on the PHP and Zend websites, or use PHPize. The Midgard PHP extension, as distributed, should be ready to build as an .so, but if you don't have phpize you're SOL. On my Redhat 7.1 system, it's in /usr/bin. -- JustThe.net LLC - Steve "Web Dude" Sobol, CTO ICQ: 56972932/WebDude216 website: http://JustThe.net email: [EMAIL PROTECTED] phone: 216.619.2NET postal: 5686 Davis Drive, Mentor On The Lake, OH 44060-2752 DalNet: ZX-2
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
