[Bug libgcc/99964] android(bionic) cannot find crti.o and crtn.o on aarch64

2021-08-04 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99964

Andrew Pinski  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #10 from Andrew Pinski  ---
There is really no support for aarch64-linux-android included.  The target
headers for aarch64 don't include any support at all.

*** This bug has been marked as a duplicate of bug 101785 ***

[Bug libgcc/99964] android(bionic) cannot find crti.o and crtn.o on aarch64

2021-04-08 Thread unlvsur at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99964

--- Comment #9 from cqwrteur  ---
(In reply to Marek Polacek from comment #7)
> Why do you keep adding Jakub to CC?  He's not a mingw maintainer.

You get the same error on Linux hosted system too because gcc needs to find
crti.o and crtn.o for aarch64-linux-android targets, no matter what hosted
system you are. It has nothing to do with MinGW-w64 or Msys2 etc.

[Bug libgcc/99964] android(bionic) cannot find crti.o and crtn.o on aarch64

2021-04-08 Thread unlvsur at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99964

--- Comment #8 from cqwrteur  ---
(In reply to Marek Polacek from comment #7)
> Why do you keep adding Jakub to CC?  He's not a mingw maintainer.

This is not mingw issue. it is libgcc's issue.

[Bug libgcc/99964] android(bionic) cannot find crti.o and crtn.o on aarch64

2021-04-08 Thread mpolacek at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99964

Marek Polacek  changed:

   What|Removed |Added

 CC||mpolacek at gcc dot gnu.org

--- Comment #7 from Marek Polacek  ---
Why do you keep adding Jakub to CC?  He's not a mingw maintainer.

[Bug libgcc/99964] android(bionic) cannot find crti.o and crtn.o on aarch64

2021-04-08 Thread unlvsur at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99964

cqwrteur  changed:

   What|Removed |Added

 CC||jakub at gcc dot gnu.org

--- Comment #6 from cqwrteur  ---
Hi Jakub.
Any guideline on how to remove crti.o and crtn.o requirement in libgcc for
aarch64-linux-android? I would like to submit a patch to support android (for
x86_64, i686, armv7 and aarch64) on GCC, including the bug fix of libstdc++.

[Bug libgcc/99964] android(bionic) cannot find crti.o and crtn.o on aarch64

2021-04-07 Thread unlvsur at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99964

--- Comment #5 from cqwrteur  ---
(In reply to Jim Wilson from comment #1)
> (In reply to cqwrteur from comment #0)
> > bionic simply does not provide crti.o and crtn.o
> > https://github.com/aosp-riscv/platform_bionic/tree/master/libc/arch-common/
> > bionic
> 
> That is the RISC-V Android port in progress.  It should not be used for
> anything other than RISC-V, as RISC-V patches might have accidentally broken
> other targets.  Use the official Android sources for Aarch64, or maybe
> something distributed by Linaro.

build of arm-linux-androideabi-g++ is successful too. So it is aarch64 specific
issue for android in libgcc. I think Jakub can help me fix it.

[Bug libgcc/99964] android(bionic) cannot find crti.o and crtn.o on aarch64

2021-04-07 Thread unlvsur at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99964

--- Comment #4 from cqwrteur  ---
(In reply to cqwrteur from comment #3)
> (In reply to Jim Wilson from comment #1)
> > (In reply to cqwrteur from comment #0)
> > > bionic simply does not provide crti.o and crtn.o
> > > https://github.com/aosp-riscv/platform_bionic/tree/master/libc/arch-common/
> > > bionic
> > 
> > That is the RISC-V Android port in progress.  It should not be used for
> > anything other than RISC-V, as RISC-V patches might have accidentally broken
> > other targets.  Use the official Android sources for Aarch64, or maybe
> > something distributed by Linaro.
> 
> 
> This is my x86_64-linux-android toolchain. I does not need crti and crtn tbh.
> https://github.com/expnkx/Windows-Hosted-x86_64-linux-android-GCC-Cross-
> Compiler

It does not need crti and crtn tbh.

[Bug libgcc/99964] android(bionic) cannot find crti.o and crtn.o on aarch64

2021-04-07 Thread unlvsur at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99964

--- Comment #3 from cqwrteur  ---
(In reply to Jim Wilson from comment #1)
> (In reply to cqwrteur from comment #0)
> > bionic simply does not provide crti.o and crtn.o
> > https://github.com/aosp-riscv/platform_bionic/tree/master/libc/arch-common/
> > bionic
> 
> That is the RISC-V Android port in progress.  It should not be used for
> anything other than RISC-V, as RISC-V patches might have accidentally broken
> other targets.  Use the official Android sources for Aarch64, or maybe
> something distributed by Linaro.


This is my x86_64-linux-android toolchain. I does not need crti and crtn tbh.
https://github.com/expnkx/Windows-Hosted-x86_64-linux-android-GCC-Cross-Compiler

[Bug libgcc/99964] android(bionic) cannot find crti.o and crtn.o on aarch64

2021-04-07 Thread unlvsur at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99964

--- Comment #2 from cqwrteur  ---
(In reply to Jim Wilson from comment #1)
> (In reply to cqwrteur from comment #0)
> > bionic simply does not provide crti.o and crtn.o
> > https://github.com/aosp-riscv/platform_bionic/tree/master/libc/arch-common/
> > bionic
> 
> That is the RISC-V Android port in progress.  It should not be used for
> anything other than RISC-V, as RISC-V patches might have accidentally broken
> other targets.  Use the official Android sources for Aarch64, or maybe
> something distributed by Linaro.

i successfully built my own android linux toolchain on x86_64.
i think this is just a bug in libgcc since crti.o and crtn.o should not get
included.

[Bug libgcc/99964] android(bionic) cannot find crti.o and crtn.o on aarch64

2021-04-07 Thread wilson at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99964

Jim Wilson  changed:

   What|Removed |Added

 CC||wilson at gcc dot gnu.org

--- Comment #1 from Jim Wilson  ---
(In reply to cqwrteur from comment #0)
> bionic simply does not provide crti.o and crtn.o
> https://github.com/aosp-riscv/platform_bionic/tree/master/libc/arch-common/
> bionic

That is the RISC-V Android port in progress.  It should not be used for
anything other than RISC-V, as RISC-V patches might have accidentally broken
other targets.  Use the official Android sources for Aarch64, or maybe
something distributed by Linaro.