This is the mail archive of the
mailing list for the GCC project.
Re: Offloading compilers' support libraries
- From: Ilya Verbin <iverbin at gmail dot com>
- To: Thomas Schwinge <thomas at codesourcery dot com>
- Cc: Bernd Schmidt <bernds at codesourcery dot com>, Jakub Jelinek <jakub at redhat dot com>, gcc-patches at gcc dot gnu dot org, Kirill Yukhin <kirill dot yukhin at gmail dot com>
- Date: Fri, 20 Feb 2015 18:05:01 +0300
- Subject: Re: Offloading compilers' support libraries
- Authentication-results: sourceware.org; auth=none
- References: <CAFiYyc11FF2EeOQzqVmQu=q9-Uh-YCN0e38jUn-jmhD9gUrWsw at mail dot gmail dot com> <20150216210812 dot GO1746 at tucnak dot redhat dot com> <20150217133206 dot GA62715 at msticlxl57 dot ims dot intel dot com> <20150217153918 dot GX1746 at tucnak dot redhat dot com> <alpine dot DEB dot 2 dot 10 dot 1502171619550 dot 19294 at digraph dot polyomino dot org dot uk> <20150217164033 dot GY1746 at tucnak dot redhat dot com> <54E5ACCE dot 7080502 at codesourcery dot com> <8761aydt4y dot fsf at schwinge dot name> <54E5D234 dot 9050209 at codesourcery dot com> <873862drj2 dot fsf at schwinge dot name>
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
> 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 ?