During the recent discussion about cross compilers I was told "bugs
happen", so I went hunting.
I have been digging into why building a cross compiler dies in different
ways for different targets.
As seen below, the Linux targets which use glibc define
MD_UNWIND_SUPPORT and have
a customized lin
On Mon, Aug 27, 2007 at 03:29:23PM -0500, Stephen M. Kenton wrote:
> As seen below, the Linux targets which use glibc define MD_UNWIND_SUPPORT and
> have
> a customized linux-unwind.h file. However, mips and i386 start and end those
> files with
> #ifndef inhibit_libc #endif statements whic
Stephen M. Kenton wrote:
During the recent discussion about cross compilers I was told "bugs
happen", so I went hunting.
I have been digging into why building a cross compiler dies in different
ways for different targets.
As seen below, the Linux targets which use glibc define
MD_UNWIND_SUPPORT
David Daney wrote:
You never state what you are trying to build. "cross compiler" does
not really narrow it down.
Also you don't state what errors you are experiencing.
I'm experimenting with building a Linux based cross compiler/tool-chain
for building the Kernel and Apps
for every target in
