On Fri, Feb 20, 2015 at 18:05:01 +0300, Ilya Verbin wrote: > On Thu, Feb 19, 2015 at 13:17:37 +0100, Thomas Schwinge wrote: > > My asumption is that it is always safe to install non-native (that is > > cross) GCC installations into the same prefix. (Which would resolve this > > problem of clashing file names for target and offloading compilers for > > good.) > > > > So, the next question is, instead of this special handling, why can't we > > require the offloading compilers to always be configured as cross > > compilers? Or, why is it a requirement that the intelmic offloading > > compiler is configured as a native compiler? > > If I understand correctly, to build a cross compiler, we need to specify a > path > to the target sysroot, even for x86_64-pc-linux-gnu to > x86_64-intelmic-linux-gnu > cross. Or is it possible to build a cross compiler without --with-sysroot ?
To be precise, for the cross compiler we need to specify a path to --with-build-time-tools (rather than --with-sysroot). The problem is that for Intel MIC there are no special as/ld/etc. So, is there an elegant way to build a cross compiler with host's build time tools? Thanks, -- Ilya
