This is the mail archive of the
newlib@sources.redhat.com
mailing list for the newlib project.
Re: Newlib doubt
- To: Bharani Chadalavada <bharani dot chadalavada at nexsi dot com>
- Subject: Re: Newlib doubt
- From: "J. Johnston" <jjohnstn at cygnus dot com>
- Date: Wed, 28 Feb 2001 13:56:11 -0500
- CC: newlib at sourceware dot cygnus dot com
- Organization: Red Hat Inc.
- References: <3A9C635E.10D11313@nexsi.com>
Bharani Chadalavada wrote:
>
> Hi,
>
> I was trying to compile newlib using an i386->mips cross gcc. I have a
> couple of questions.
> I realize that I need to provide my own implementation of close, read,
> write etc for my applications to work. But when I tried the above
> compilation, newlib needed the following header files - machine/ansi.h,
> stddef.h, limits.h etc.(this is just a partial list). Now what I don't
> understand is, do I have to have these header files as target specific
> stuff since I am compiling newlib as a target library or do I have to
> have these stuff from the native host which is i386.
> I was able to compile newlib when I gave the i386 specific header files
> in the include path. But I am not sure if this is the right thing.
>
> I really appreciate your time and help.
>
> Thank you,
> Bharani.
Bharani,
You need to compile newlib for the target which in this case is mips.
The header files in question should be supplied by your cross-compiler. What did you specify when
you configured newlib and did you personally build the cross-compiler?
-- Jeff J.