public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/99499] build failure for android bionic toolchains. error: '_U' was not declared in this scope
Date: Wed, 10 Mar 2021 16:20:15 +0000	[thread overview]
Message-ID: <bug-99499-4-bxwfH3XtgG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99499-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from cqwrteur <unlvsur at live dot com> ---
(In reply to Jonathan Wakely from comment #2)
> Obviously _U worked at some point when that file was added. CCing Maxim to
> figure out what changed and whether we want to support the old ctype
> constants as well as whatever Android defines now.

I guess now Android has now shifted to LLVM and no one tested that on GCC
anymore.

I tweak around the value by myself and no it does not work, unfortunately.

d:/msys64/x86_64-linux-android/bin/../lib/gcc/x86_64-linux-android/11.0.1/../../../../x86_64-linux-android/bin/ld.exe:
d:/msys64/x86_64-linux-android/bin/../lib/gcc/x86_64-linux-android/11.0.1/../../../../x86_64-linux-android/lib/../lib64/libstdc++.so:
undefined reference to `std::ctype<char>::ctype(unsigned short const*, bool,
unsigned long)'
d:/msys64/x86_64-linux-android/bin/../lib/gcc/x86_64-linux-android/11.0.1/../../../../x86_64-linux-android/bin/ld.exe:
d:/msys64/x86_64-linux-android/bin/../lib/gcc/x86_64-linux-android/11.0.1/../../../../x86_64-linux-android/lib/../lib64/libstdc++.so:
undefined reference to `std::ctype<char>::ctype(unsigned short const*, bool,
unsigned long)'
d:/msys64/x86_64-linux-android/bin/../lib/gcc/x86_64-linux-android/11.0.1/../../../../x86_64-linux-android/bin/ld.exe:
d:/msys64/x86_64-linux-android/bin/../lib/gcc/x86_64-linux-android/11.0.1/../../../../x86_64-linux-android/lib/../lib64/libstdc++.so:
undefined reference to `std::ctype<char>::ctype(int*, unsigned short const*,
bool, unsigned long)'
collect2.exe: error: ld returned 1 exit status


Looks like we need actual values.

  parent reply	other threads:[~2021-03-10 16:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10  0:08 [Bug libstdc++/99499] New: bootstrap failure for " unlvsur at live dot com
2021-03-10  0:25 ` [Bug libstdc++/99499] build failure for android " unlvsur at live dot com
2021-03-10 12:10 ` [Bug target/99499] " redi at gcc dot gnu.org
2021-03-10 16:20 ` unlvsur at live dot com [this message]
2021-03-10 20:53 ` unlvsur at live dot com
2021-03-10 21:07 ` unlvsur at live dot com
2021-03-10 21:47 ` unlvsur at live dot com
2021-03-10 23:52 ` unlvsur at live dot com
2021-03-10 23:54 ` unlvsur at live dot com
2021-03-10 23:55 ` unlvsur at live dot com
2023-02-19 23:11 ` lbr-dev at yandex dot com

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-99499-4-bxwfH3XtgG@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).