__DYNAMIC_REENT__ part of external API?

Jonathan S. Shapiro shap@eros-os.org
Tue Oct 1 03:43:00 GMT 2013

If I build a version of newlib with __DYNAMIC_REENT__ defined at the
time of build, does __DYNAMIC_REENT__ also need to be defined when
client code (i.e. code that calls newlib) is compiled?

The only use (consumption) of __DYNAMIC_REENT__ that I see in the
newlib headers is in libc/include/sys/reent.h, where it wraps an
extern declaration of __getreent(). Offhand, I don't think that entry
point needs to be generally available to clients.



More information about the Newlib mailing list