Packaging native newlib
Shaun Jackman
sjackman@gmail.com
Wed Jan 12 19:47:00 GMT 2005
newlib currently doesn't build anything on amd64, where config.guess
returns x86_64-unknown-linux-gnu. If configure et al. were coaxed to
build a native libarary, would the resulting binaries be correct?
Thanks,
Shaun
On Thu, 02 Dec 2004 19:18:27 -0500, Jeff Johnston <jjohnstn@redhat.com> wrote:
> 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.
More information about the Newlib
mailing list