>> On 09/28/2011 06:39 AM, Steven M. Schweda wrote: >>> From: Micah Cowan<[email protected]> >>>> In this case, the logic that does a rename of snprintf seems to be at >>>> the end of "vasnprintf.h" rather than directly in snprintf.c. >>> >>> Those aren't the droids you're looking for. Try "lib/stdio.in.h" >>> (which I also try very hard to ignore). >> >> Yes, but lib/stdio.in.h isn't included directly by snprintf.c, as >> vasnprintf.h is. The bit I'm talking about is indeed in vasnprintf.h, >> which is what actually does the rename of the link name. > > What, exactly, do you see where, exactly? All I see in > "lib/vasnprintf.h" is stuff like: > # define vasnprintf rpl_vasnprintf > # define asnprintf rpl_asnprintf > and neither "vasnprintf" nor "asnprintf" looks quite like "snprintf" to > me.
You're right, of course, and I'm blind today. I guess it must get the "lib/stdio.in.h" version after all. Probably through a judicious application of -I. Anyhoo, good luck. :) -- Micah J. Cowan http://micah.cowan.name/
