This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/70464] [arch64] create a self hosting compiler
- From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 30 Mar 2016 17:01:40 +0000
- Subject: [Bug target/70464] [arch64] create a self hosting compiler
- Auto-submitted: auto-generated
- References: <bug-70464-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70464
--- Comment #5 from ktkachov at gcc dot gnu.org ---
(In reply to georg from comment #0)
> During our approach to get the raspberry pi3 and gentoo with an aarch64
> kernel and userland running i tried to cross compile a "native compiler for
> aarch64".
>
> Our attempt succedded, as we got the userland cross compiled and the kernel.
> Both are running and seem to be ok, as far as we can tell currently. There
> is one core component for gentoo missing: The gcc.
>
> I tried to cross compile with the added cross compiler script. I used
> crossdev to create the amd64 to aarch64 cross compiler. With gcc 5.3.0 i
> could create a toolchain which runs on aarch64 but only supports C. No C++.
> You can download the folder here:
> https://www.schorsch-tech.de/rpi3/cross.tar.bz2
>
I usually use the target aarch64-none-linux-gnu, but aarch64-linux-gnu should
work too.
Note that GCC requires a C++ compiler to build, so trying to use a C-only
compiler can't work.
If I understand correctly, you want to build an aarch64-to-aarch64 compiler on
an x86_64-linux host, and you've only managed to do that for the C frontend?
What was the gcc configure line passed to that build (by crossdev, or whatever)
Passing "-v" to the C-only gcc would give that information...