Patches to detect newlib changes

[Joel Sherrill]

Hi

Jennifer and I have a series of changes pending to RTEMS
that add cpuset tests, pthread affinity APIs and Classic API
affinity APIs. These depend on the presence of certain
prototypes and data types in newlib.

In an attempt to keep things building with old tools, I
have attached a set of patches that I think can be used
to detect enough of the changes to let git bisect
continue to work across the tool changes.

For sure, our (unmerged) code will have to use the proper
conditionals to prevent itself from being compiled.

The one I don't know about it Sebastian's re-implementation
of pthread cleanup push/pop. I don't know how to detect that
change.

How do these patches look? And any suggestions?

The changes to newlib are on the cvs head -- pthread.h and
cpuset.h primarily.


-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill at OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
Support Available                (256) 722-9985
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-psxtests-configure.ac-Probe-for-SMP-affinity-methods.patch
Type: text/x-patch
Size: 1852 bytes
Desc: not available
URL: <http://lists.rtems.org/pipermail/devel/attachments/20131209/f908e98b/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-cpukit-configure.ac-Probe-for-SMP-affinity-methods.patch
Type: text/x-patch
Size: 1248 bytes
Desc: not available
URL: <http://lists.rtems.org/pipermail/devel/attachments/20131209/f908e98b/attachment-0001.bin>