This is the mail archive of the
newlib@sources.redhat.com
mailing list for the newlib project.
Re: Packaging native newlib
- From: Shaun Jackman <sjackman at gmail dot com>
- To: Jeff Johnston <jjohnstn at redhat dot com>
- Cc: newlib at sources dot redhat dot com
- Date: Wed, 12 Jan 2005 11:47:01 -0800
- Subject: Re: Packaging native newlib
- References: <7f45d939041202145270f55c3e@mail.gmail.com> <41AFA314.2020407@redhat.com> <7f45d939041202153716a865ac@mail.gmail.com> <41AFB0D3.8020109@redhat.com>
- Reply-to: Shaun Jackman <sjackman at gmail dot com>
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.