> I'm not sure if we should do this.  The autoconf manual section on
> Particular Function Checks says:
>
> "If the malloc function is compatible with the GNU C library malloc (i.e.,
> `malloc (0)' returns a valid pointer), define HAVE_MALLOC to 1. Otherwise
> define HAVE_MALLOC to 0, ask for an AC_LIBOBJ replacement for `malloc',
> and define malloc to rpl_malloc so that the native malloc is not used in
> the main project."

Personally, I think we're working too hard to try to solve a problem
that will happen only when zero bytes are requested.  That should never
happen -- if it does, it's a bug in x5250, not in Solaris.

My opinion is that you should remove the autoconf macro.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.