palardyn at mac.com
Fri Oct 19 12:43:16 EDT 2001
Seeing as how I did both I'm going to remove malloc.h and see if it will
That way we should know if the cp is sufficient by itself
On Thursday, October 18, 2001, at 09:47 PM, Mark J. Lilback wrote:
> At 8:50 PM -0400 10/18/01, James K. Lowden wrote:
>> As editor-in-chief rumormonger, I'd like to know (if you know): Are the
>> config files you had Norman copy supposed to have some intelligence
>> about the (non)existence of malloc.h? That is: Is the presence of
>> /usr/include/malloc.h required or irrelevant?
> They don't specifically, but it probably chains to that. They just give
> the canonical machine/os type so the configure script will work
> properly. I'd assume a working config script would then figure out if
> malloc.h should be included or not.
> That's pure guess work on my part, as I don't know much about these
> except that they are shell scripts I can hack if I'm having problems
> with a port.
> "They that can give up essential
> Mark J. Lilback to obtain a little temporary safety
> <mark at lilback.com> deserve neither liberty or safety."
> http://www.lilback.com/ -- Benjamin
> You are currently subscribed to freetds as: [norm at kirais.com]
> To unsubscribe, forward this message to leave-
> freetds-136003B at franklin.oit.unc.edu
More information about the FreeTDS