| |||||||||||||
Isn't that what autoconf is for?Isn't that what autoconf is for?Posted May 21, 2009 10:50 UTC (Thu) by alex (subscriber, #1355)In reply to: That's silly. You can have strlcat() and strlcpy(), yet be compatible by sbishop Parent article: EGLIBC: Not a fork, but a glibc distribution
Doesn't autoconf check for these sort of things? I would assume packages that compile on BSD and GNU systems already have #ifdef HAS_STRLCAT or something similar.
(Log in to post comments)
Isn't that what autoconf is for? Posted May 21, 2009 17:10 UTC (Thu) by jschrod (subscriber, #1646) [Link]
This is about binary compatibility, not source compatibility. `Drop-in replacement' means that one doesn't have to compile applications anew when one exchanges one glibc for the other.
|
|||||||||||||