Kai Ruottu <[EMAIL PROTECTED]> writes:
> For which existing targets the prebuilt C libraries are missing? Or
> which are the
> targets which don't have any "suitable", "compatible" or something C library
> which could serve as that temporary bootstrap "target C library"
> during the GCC
> build?
Ian Lance Taylor wrote :
Kai Ruottu <[EMAIL PROTECTED]> writes:
Ok, the traditional "evolutionary" method is to not reinvent the wheel
with the already tested target components but let then be as they are
and produce only the stuff required for the new $host, the GNU
binutils and the GCC s
Kai Ruottu <[EMAIL PROTECTED]> writes:
> Ok, the traditional "evolutionary" method is to not reinvent the wheel
> with the already tested target components but let then be as they are
> and produce only the stuff required for the new $host, the GNU
> binutils and the GCC sources. NOT the target
Hi Kai,
I agree that the things I wrote does not have much sense for people
that spent years in developing GCC, like you and most of the people
here are. I am very very very new in both using gcc and in its
internals. The first time when I was building cross platform gcc I
really did it from the
Ferad Zyulkyarov wrote :
To build a GCC corss compiler it would be good to use a specail tool
that is called "crosstool". You may look at the following links:
1. http://kegel.com/crosstool/
2. http://kegel.com/crosstool/current/doc/crosstool-howto.html
Everyone always building the target Linux
To build a GCC corss compiler it would be good to use a specail tool
that is called "crosstool". You may look at the following links:
1. http://kegel.com/crosstool/
2. http://kegel.com/crosstool/current/doc/crosstool-howto.html
On 2/9/07, Bhaskar Reddy <[EMAIL PROTECTED]> wrote:
> Build binut
