Packaging native newlib

[Jeff Johnston]

Platforms have the ability to override headers with machine-specific versions. 
Ther are also shared headers in the libc/include directory.  Obviously, 
machine-specific headers are not portable.  You say native newlib.  Well, newlib 
is only native in a few rare cases.  Cygwin for example, and linux as anothe 
example.  Linux currently is only supported for x86.  If it was supported for 
another platform, say, arm-linux, then there would be machine-specific versions 
of some of the headers in libc/sys/linux/machine/xxxx.  Look at the 
install-data-local target in Makefile.am.

-- Jeff J.

Shaun Jackman wrote:
> The package is being built on x86 Linux, but I'd like to know if the
> newlib headers files are portable accross the Debian architectures:
> alpha arm hppa hurd-i386 i386 ia64 m68k mips mipsel powerpc s390 sparc.
> 
> Thanks,
> Shaun
> 
> 
> On Thu, 02 Dec 2004 18:19:48 -0500, Jeff Johnston <jjohnstn@redhat.com> wrote:
> 
>>Assuming you are referring to x86 Linux and the choice of i386, i486, i586,
>>etc.: the installed newlib header files are currently the same.
>>
>>-- Jeff J.
>>
>>
>>Shaun Jackman wrote:
>>
>>>When building newlib natively, do the installed headers differ at all
>>>depending on the architecture of the system on which it's being built?
>>>I'm trying to decide whether the newlib-headers package needs to be
>>>built for each architecture individually, or whether one package will
>>>be suitable for all architectures.
>>>
>>>Please cc me in your reply. Thanks,
>>>Shaun