This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug target/70464] [arch64] create a self hosting compiler


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70464

--- Comment #7 from georg@schorsch-tech.de ---
(In reply to ktkachov from comment #5)
> 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...

Yes, you are right. I want on an amd64 host compile a "aarch64 to aarch64"
compiler.

This is the required information. Right from the target

Pi_3 64_bit ~ # gcc -v   
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/opt/cross/libexec/gcc/aarch64-linux-gnu/5.3.0/lto-wrapper
Target: aarch64-linux-gnu
Configured with: ../gcc-5.3.0/configure --prefix=/opt/cross
--host=aarch64-linux-gnu --target=aarch64-linux-gnu --enable-languages=c
--disable-multilib
Thread model: posix
gcc version 5.3.0 (GCC)

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]