This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: AW: AW: EABI
- From: Andrew Haley <aph at redhat dot com>
- To: "Warlich, Christof" <christof dot warlich at siemens dot com>
- Cc: Ian Lance Taylor <iant at google dot com>, "gcc-help at gcc dot gnu dot org" <gcc-help at gcc dot gnu dot org>
- Date: Fri, 18 Oct 2013 09:56:45 +0100
- Subject: Re: AW: AW: EABI
- Authentication-results: sourceware.org; auth=none
- References: <6D83E89737156549AEA25EF9ED712C5D04EA95 at DEFTHW99EK1MSX dot ww902 dot siemens dot net> <80070575041F1A43B43673DA71C5B0BCBBE2B2EE65 at INBLRK77M1MSX dot in002 dot siemens dot net> <6D83E89737156549AEA25EF9ED712C5D04EADD at DEFTHW99EK1MSX dot ww902 dot siemens dot net> <525FA924 dot 8050504 at redhat dot com> <6D83E89737156549AEA25EF9ED712C5D04EB1E at DEFTHW99EK1MSX dot ww902 dot siemens dot net> <CAKOQZ8xKdciCkvU_R99nXDhZzpVkc9sdDBLb2yWgu0t4R82NWQ at mail dot gmail dot com> <6D83E89737156549AEA25EF9ED712C5D04EBE3 at DEFTHW99EK1MSX dot ww902 dot siemens dot net>
On 10/18/2013 06:54 AM, Warlich, Christof wrote:
> Well, I more or less inherited a poorly structured toolchain build
> environment for the target architectures i686, mibsel, mipseb, arm
> and powerpc, all for Linux, and I urgently need to do some cleanup
> work, as new versions for these architectures are to be supported in
> the future. And even when using crosstool-ng to do this task, I
> wanted to know which changes in the target tuple do really affect
> toolchain generation and which ones don't, but are to be recommended
> from the conventional point of view.
Any GNU/Linux cross-compiler that you use must be built against the
system that it is targeting. This is not just because of the ABI, but
because it is built against the target's headers and libraries. You
cannot use a cross-compiler built for one system to build for another.
Andrew.