This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
> It seems a chicken and egg problem: glibc needs gcc, gcc needs glibc. It is. You need a robot chicken to make your first egg. Specifically, you build a stripped-down gcc that is enough to build glibc, then use that two to build the final gcc. > What can I do? Fortunately there are tools to help you. crosstool-ng is the probably what you need: a cross compiler building tool, complete with lots of knowledge of special options and incantations for different versions of the various software components and for different processor architecture and library combinations. There is also the privately developed but open source OSELAS.ToolChain(), whose cross-compiler builder is part of a larger system for cross-building finely tuned root filesystems. By looking inside them, or at their log files, you can find the exact sequence of commands they issue to do the work. Depnding on your software distribution and host operating system, you may also find prebuilt crosscompilers: emdebian's repository of cross-compilers are good, and gentoo's crossdev stuff and OpenEmbedded also address the problem. Good luck! M -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |