php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #20977 Cannot compile both yaz and imap options
Submitted: 2002-12-12 18:43 UTC Modified: 2002-12-15 15:29 UTC
From: vgl at palni dot edu Assigned:
Status: Closed Package: Compile Failure
PHP Version: 4.3.0RC3 OS: Solaris 2.9
Private report: No CVE-ID: None
 [2002-12-12 18:43 UTC] vgl at palni dot edu
   With php-4.3.0RC3 on Solaris 2.9, the 'imap' and 'yaz' extensions seem to have a conflict.  That is, I get compilation errors after the following configure command:

      configure --with-imap --with-yaz

The make fails with:
  

  /bin/sh libtool --silent --mode=link gcc -export-dynamic -g -O2  -L/usr/ucblib -L/usr/local/lib/gcc-lib/sparc-sun-solaris2.9/2.95.3 -L/usr/local/lib  -R /usr/ucblib -R /usr/local/lib/gcc-lib/sparc-sun-solaris2.9/2.95.3 -R /usr/local/lib ext/ctype/ctype.lo ext/imap/php_imap.lo ext/mysql/php_mysql.lo ext/mysql/libmysql/libmysql.lo ext/mysql/libmysql/errmsg.lo ext/mysql/libmysql/net.lo ext/mysql/libmysql/violite.lo ext/mysql/libmysql/password.lo ext/mysql/libmysql/my_init.lo ext/mysql/libmysql/my_lib.lo ext/mysql/libmysql/my_static.lo ext/mysql/libmysql/my_malloc.lo ext/mysql/libmysql/my_realloc.lo ext/mysql/libmysql/my_create.lo ext/mysql/libmysql/my_delete.lo ext/mysql/libmysql/my_tempnam.lo ext/mysql/libmysql/my_open.lo ext/mysql/libmysql/mf_casecnv.lo ext/mysql/libmysql/my_read.lo ext/mysql/libmysql/my_write.lo ext/mysql/libmysql/errors.lo ext/mysql/libmysql/my_error.lo ext/mysql/libmysql/my_getwd.lo ext/mysql/libmysql/my_div.lo ext/mysql/libmysql/mf_pack.lo ext/mysql/libmysql/my_messnc.lo ext/mysql/libmysql/mf_dirname.lo ext/mysql/libmysql/mf_fn_ext.lo ext/mysql/libmysql/mf_wcomp.lo ext/mysql/libmysql/typelib.lo ext/mysql/libmysql/safemalloc.lo ext/mysql/libmysql/my_alloc.lo ext/mysql/libmysql/mf_format.lo ext/mysql/libmysql/mf_path.lo ext/mysql/libmysql/mf_unixpath.lo ext/mysql/libmysql/my_fopen.lo ext/mysql/libmysql/mf_loadpath.lo ext/mysql/libmysql/my_pthread.lo ext/mysql/libmysql/my_thr_init.lo ext/mysql/libmysql/thr_mutex.lo ext/mysql/libmysql/mulalloc.lo ext/mysql/libmysql/string.lo ext/mysql/libmysql/default.lo ext/mysql/libmysql/my_compress.lo ext/mysql/libmysql/array.lo ext/mysql/libmysql/my_once.lo ext/mysql/libmysql/list.lo ext/mysql/libmysql/my_net.lo ext/mysql/libmysql/dbug.lo ext/mysql/libmysql/strmov.lo ext/mysql/libmysql/strxmov.lo ext/mysql/libmysql/strnmov.lo ext/mysql/libmysql/strmake.l

  /usr/local/lib/libyaz.a(unix.o): In function `unix_close':
  /usr/local/src/yaz/yaz-1.9.2/comstack/unix.c:565: multiple definition of `unix_close'
  /usr/local/lib/libc-client.a(unix.o):/usr/local/src/imap/imap-2002.RC2/c-client/unix.c:437: first defined here
  /usr/local/sparc-sun-solaris2.9/bin/ld: Warning: size of symbol `unix_close' changed from 124 to 100 in unix.o
  collect2: ld returned 1 exit status
  gmake: *** [sapi/cgi/php-cgi] Error 1


However, 'configure --with-imap' and 'configure --with-yaz' each build without errors.  Similarly, php4.2.3 does not have this problem with configured with both imap and yaz.

Thanks.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2002-12-13 02:45 UTC] sniper@php.net
Are the yaz and c-client libs the same when you tried with PHP 4.2.3 ?? And this really isn't a PHP problem, both c-client and yaz libs use same names for their functions.

You really should report this to either the authors of yaz or c-client..

 [2002-12-13 08:45 UTC] vgl at palni dot edu
Yes, the versions of yaz and the imap c-client libraries were the same with php 4.2.3, and I did not encounter any build errors using the same configure options.

I'll share the problem with the yaz and c-client developers.  Thanks.
 [2002-12-15 15:29 UTC] dickmeiss@php.net
Problem is fixed by marking the function unix_close 'static'
in yaz/comstack/unix.c. Fixed in CVS version of YAZ
and next version of YAZ (1.9.3).

 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved.
Last updated: Fri Aug 01 13:00:03 2025 UTC