Bug #16891 Compile of "mf_keycache.c" without --enable-thread-safe-client
Submitted: 30 Jan 2006 11:12 Modified: 16 Mar 2006 13:49
Reporter: Kent Boortz Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Compiling Severity:S3 (Non-critical)
Version:5.0.18 OS:HP/UX (HP-UX 11.23 IA-64)
Assigned to: Assigned Account CPU Architecture:Any

[30 Jan 2006 11:12] Kent Boortz
Description:
A build configured with

  ./configure --prefix=/some/path/local --disable-shared --without-server

fails, with

cc -DDEFAULT_BASEDIR=\"/home/mysqldev/merlin/local\" \ 
-DDATADIR="\"/home/mysqldev/merlin/local/var\"" \ 
-DDEFAULT_CHARSET_HOME="\"/home/mysqldev/merlin/local\"" \ 
-DSHAREDIR="\"/home/mysqldev/merlin/local/share/mysql\"" \ 
-DDEFAULT_HOME_ENV=MYSQL_HOME \ 
-DDEFAULT_GROUP_SUFFIX_ENV=MYSQL_GROUP_SUFFIX \ 
-DHAVE_CONFIG_H -I. -I. -I.. -I../zlib -I../include -I../include -I. \ 
 -DDBUG_OFF +O2 +DD64 +DSitanium2 -mt -AC99 \ 
-DPTHREAD_COMPAT_MODE -I/home/mysqldev/merlin/local/include \
-DHPUX11  -DSNPRINTF_RETURN_TRUNC -DHAVE_BROKEN_PREAD \ 
-DDONT_USE_FINITE -DHAVE_BROKEN_GETPASS \ 
-DNO_FCNTL_NONBLOCK -DDO_NOT_REMOVE_THREAD_WRAPPERS \ 
-DHAVE_BROKEN_PTHREAD_COND_TIMEDWAIT \ 
-DHAVE_BROKEN_INLINE -c mf_keycache.c

"../include/keycache.h", line 74: error #2020: identifier "pthread_mutex_t" is undefined
    pthread_mutex_t cache_lock;    /* to lock access to the cache structure    */
    ^

"mf_keycache.c", line 103: error #2020: identifier "pthread_cond_t" is undefined
  typedef pthread_cond_t KEYCACHE_CONDVAR;
          ^

"mf_keycache.c", line 171: warning #2177-D: function "test_key_cache" was declared but never referenced
  static void test_key_cache(KEY_CACHE *keycache,
              ^

2 errors detected in the compilation of "mf_keycache.c".

How to repeat:
On HP-UX 11.23 IA-64, do

  % ./configure --prefix=/some/path/local --disable-shared --without-server
  % make
[16 Mar 2006 13:49] Joerg Bruehe
Please do not submit the same bug more than once. An existing
bug report already describes this very problem. Even if you feel
that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments
to the original bug instead.

Thank you for your interest in MySQL.

Additional info:

The symptoms are identical to those of bug#15861 which is fixed by now, effective in 5.0.20.

We may have to revisit it if the issue still occurs.