Binary borkedness and memchr/strncasecmp

["William A. Rowe, Jr." <wr...@rowe-clan.net>]

If autoconf fails to pick up memchr or strncasecmp, we build those fn's
into libapr.

Unfortunately, if using a dynamic clib, and later upgrading the clib or
moving those binaries on another machine with memchr or strncasecmp
in the clib, you will blow up from multiple symbols when loading the app.

Can we please use apr_memchr and apr_strncasecmp?  I don't mind
if we #define to the platform fn's, and blow up when downgrading the
clib or moving to an older machine without those functions.

Bill

Re: Binary borkedness and memchr/strncasecmp

[Cliff Woolley <jw...@virginia.edu>]

On Mon, 8 Jul 2002, William A. Rowe, Jr. wrote:

> Can we please use apr_memchr and apr_strncasecmp?  I don't mind
> if we #define to the platform fn's, and blow up when downgrading the
> clib or moving to an older machine without those functions.

+1

--Cliff