This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Oct 8 17:24, Ralf Corsepius wrote:Depends on _COMPILING_NEWLIB's semantics.Hi,
similar to Cygwin, compiling newlib for RTEMS needs -D_COMPILING_NEWLIB.
BTW: I am wondering if -D_COMPILING_NEWLIB shouldn't be supplied globally for all targets and not only for RTEMS and Cygwin.
Ralf
2010-10-08 Ralf Cors??pius<ralf.corsepius@rtems.org>
* configure.host: Add -D_COMPILING_NEWLIB to newlib_cflags.
Patch applied. I'm not sure it's a good idea to add -D_COMPILING_NEWLIB to all targets.
I don't know how RTEMS handles it,We are treating it as a newlib-private/internal define which is not supposed to be used outside of newlib to denote the fact "we're inside of newlib" to expose newlib internal parts.
We're using #ifdef __rtems__ for rtems-specific parts and would assume all other OSes to also use an OS-specific define for their OS-specific parts.but in Cygwin it's only used in very special cases in which we have clashes between newlib and Cygwin definitions (for instance when using _off_t vs. off_t). Are you sure that all cases in which `#ifdef _COMPILING_NEWLIB' is used in newlib are also feasible for RTEMS?
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |