public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wilson at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/99964] android(bionic) cannot find crti.o and crtn.o on aarch64
Date: Wed, 07 Apr 2021 20:31:58 +0000 [thread overview]
Message-ID: <bug-99964-4-ymW0PuMqIW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99964-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99964
Jim Wilson <wilson at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wilson at gcc dot gnu.org
--- Comment #1 from Jim Wilson <wilson at gcc dot gnu.org> ---
(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.
next prev parent reply other threads:[~2021-04-07 20:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 20:16 [Bug libgcc/99964] New: android(bionic) cannot find crti.o and crtn.o unlvsur at live dot com
2021-04-07 20:31 ` wilson at gcc dot gnu.org [this message]
2021-04-07 20:33 ` [Bug libgcc/99964] android(bionic) cannot find crti.o and crtn.o on aarch64 unlvsur at live dot com
2021-04-07 20:34 ` unlvsur at live dot com
2021-04-07 20:34 ` unlvsur at live dot com
2021-04-07 22:52 ` unlvsur at live dot com
2021-04-09 0:28 ` unlvsur at live dot com
2021-04-09 0:34 ` mpolacek at gcc dot gnu.org
2021-04-09 0:35 ` unlvsur at live dot com
2021-04-09 0:37 ` unlvsur at live dot com
2021-08-05 0:37 ` pinskia at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-99964-4-ymW0PuMqIW@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).