On Thu, Oct 17, 2013 at 2:51 AM, Warlich, Christof <christof.warlich@xxxxxxxxxxx> wrote: > > 1) Does is make a difference (w.r.t. ABI use?) if building a toolchain for i686 depending on whether I pass > --target=i686-mytoolchain-linux-gnu or --target= i686-mytoolchain-linux-gnueabi to configure? > 2) Does is make a difference (w.r.t. ABI use?) if building a toolchain for powerpc depending on whether I pass > --target=powerpc-mytoolchain-linux-gnu or --target= powerpc-mytoolchain-linux-gnueabi to configure? > 3) Again, does is make a difference (w.r.t. ABI use?) if building a toolchain for powerpc depending on whether I pass > --target=powerpc-mytoolchain-linux-eabi or --target= powerpc-mytoolchain-linux-gnueabi to configure? Why are you asking these questions? Is this really what you want to know? To me these questions seem the wrong way around. What matters is what ABIs are out there and what systems support them. The way the toolchain handles them is secondary. You can answer these questions yourself by looking at gcc/config.gcc. For example, in there I see i[34567]86-*-linux* | i[34567]86-*-kfreebsd*-gnu | i[34567]86-*-knetbsd*-gnu | i[34567]86-*-gnu* | i[34567]86-*-kopensolaris*-gnu) The i[34567]86-*-gnu* string tells me that i686-mytoolchain-linux-gnu and i686-mytoolchain-linux-gnueabi are identical. Or, to put it another way, i686-mytoolchain-linux-gnueabi does not exist as a separate configuration. Ian
