Bug #17521 Updated: Compile problems with ICAP extension.

ID: 17521 Updated by: sniper@php.net Reported By: derekm@hackunix.org -Status: Open +Status: Bogus Bug Type: Compile Failure Operating System: Heavily modified Red Hat 6.2 PHP Version: 4.2.1 New Comment: Just FYI: You don't need ext/icap. MCAL extension is enough. http://www.php.net/manual/en/ref.mcal.php Previous Comments: ------------------------------------------------------------------------ [2002-05-30 13:52:40] derekm@hackunix.org I have both the MCAL and the ICAP extensions turned on. Mostly just because I can. ICAP is to calendars as IMAP is to email. I do a lil' bit of development work for the Horde Project, and I thought maybe Kronolith (Horde's calendar application) might be able to make use of the ICAP extension. ------------------------------------------------------------------------ [2002-05-30 07:20:45] sniper@php.net Why aren't you using mcal extension ?? (what is icap anyway? :) ------------------------------------------------------------------------ [2002-05-30 04:34:36] derekm@hackunix.org I'm having problems compiling PHP 4 with the ICAP extension enabled. I have the latest version on MCAL installed on my system (0.6). 'ext/icap/php_icap.c' attempts to #INCLUDE 'cal.h'--however, MCAL has no header file called 'cal.h'. It does have 'cal_misc.h' and 'mcal.h', but not 'cal.h'. In /usr/local/include/mcal, I symlinked 'cal.h' to 'cal_misc.h', and ran 'make' again. This time compilation of 'ext/icap/php_icap.c' successed. However, a few files later, it tried to compile something with '-licap'. MCAL no longer has a seperate libicap. I found that '-licap' was coming from $ICAP_SHARED_LIBADD in 'config_vars.mk'. I changed '-licap' to '-lmcal' and this second file compiled without errors. I think this generally means that the ICAP extension must be pretty out of date. Maybe somebody should do some work on it. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=17521&edit=1