public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/97911] [11 regression] make install issue undefined reference to std::__throw_bad_array_new_length after r11-5142
Date: Thu, 19 Nov 2020 19:15:42 +0000 [thread overview]
Message-ID: <bug-97911-4-hDdPuxrXMm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97911-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97911
Tamar Christina <tnfchris at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tnfchris at gcc dot gnu.org
Host|powerpc64le-linux-gnu |powerpc64le-linux-gnu,
| |aarch64-none-linux-gnu
Target|powerpc64le-linux-gnu |powerpc64le-linux-gnu,
| |aarch64-none-linux-gnu
Build|powerpc64le-linux-gnu |powerpc64le-linux-gnu,
| |aarch64-none-linux-gnu
--- Comment #1 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
I get an equally weird error during make-install for aarch64-none-linux-gnu:
../libbacktrace/.libs/libbacktrace.a(mmap.o): In function `backtrace_free':
/host-aarch64-unknown-linux-gnu/libbacktrace/../.././libbacktrace/mmap.c:229:
undefined reference to `__aarch64_swp4_acq'
../libbacktrace/.libs/libbacktrace.a(mmap.o): In function
`backtrace_alloc':
/host-aarch64-unknown-linux-gnu/libbacktrace/../.././libbacktrace/mmap.c:135:
undefined reference to `__aarch64_swp4_acq'
../libbacktrace/.libs/libbacktrace.a(elf.o): In function
`elf_add_syminfo_data':
/host-aarch64-unknown-linux-gnu/libbacktrace/../.././libbacktrace/elf.c:746:
undefined reference to `__aarch64_cas8_acq_rel'
../libbacktrace/.libs/libbacktrace.a(elf.o): In function
`backtrace_initialize':
../.././gcc/lto/Make-lang.in:100: recipe for target 'lto-dump' failed
/host-aarch64-unknown-linux-gnu/libbacktrace/../.././libbacktrace/elf.c:4906:
undefined reference to `__aarch64_cas8_acq_rel'
../libbacktrace/.libs/libbacktrace.a(dwarf.o): In function
`backtrace_dwarf_add':
/host-aarch64-unknown-linux-gnu/libbacktrace/../.././libbacktrace/dwarf.c:4045:
undefined reference to `__aarch64_cas8_acq_rel'
collect2: error: ld returned 1 exit status
make[2]: *** [lto-dump] Error 1
../libbacktrace/.libs/libbacktrace.a(mmap.o): In function `backtrace_free':
/host-aarch64-unknown-linux-gnu/libbacktrace/../.././libbacktrace/mmap.c:229:
undefined reference to `__aarch64_swp4_acq'
../libbacktrace/.libs/libbacktrace.a(mmap.o): In function
`backtrace_alloc':
/host-aarch64-unknown-linux-gnu/libbacktrace/../.././libbacktrace/mmap.c:135:
undefined reference to `__aarch64_swp4_acq'
../libbacktrace/.libs/libbacktrace.a(elf.o): In function
`elf_add_syminfo_data':
/host-aarch64-unknown-linux-gnu/libbacktrace/../.././libbacktrace/elf.c:746:
undefined reference to `__aarch64_cas8_acq_rel'
../libbacktrace/.libs/libbacktrace.a(elf.o): In function
`backtrace_initialize':
/host-aarch64-unknown-linux-gnu/libbacktrace/../.././libbacktrace/elf.c:4906:
undefined reference to `__aarch64_cas8_acq_rel'
../.././gcc/cp/Make-lang.in:121: recipe for target 'cc1plus' failed
../libbacktrace/.libs/libbacktrace.a(dwarf.o): In function
`backtrace_dwarf_add':
make[2]: Leaving directory '/host-aarch64-unknown-linux-gnu/gcc'
/host-aarch64-unknown-linux-gnu/libbacktrace/../.././libbacktrace/dwarf.c:4045:
undefined reference to `__aarch64_cas8_acq_rel'
collect2: error: ld returned 1 exit status
make[2]: *** [cc1plus] Error 1
Makefile:5133: recipe for target 'install-gcc' failed
make[1]: Leaving directory ''
make[1]: *** [install-gcc] Error 2
Makefile:2446: recipe for target 'install' failed
make: *** [install] Error 2
etc for each install target. I have only been able to reproduce it when
bootstrap enabled and haven't been able to on Ubuntu 18.04 but can on Debian
9..
next prev parent reply other threads:[~2020-11-19 19:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 16:42 [Bug other/97911] New: " seurer at gcc dot gnu.org
2020-11-19 19:15 ` tnfchris at gcc dot gnu.org [this message]
2020-11-19 19:47 ` [Bug other/97911] " jakub at gcc dot gnu.org
2020-11-19 23:21 ` tnfchris at gcc dot gnu.org
2020-11-19 23:24 ` ebotcazou at gcc dot gnu.org
2020-11-19 23:30 ` jakub at gcc dot gnu.org
2020-11-20 7:50 ` cvs-commit at gcc dot gnu.org
2020-11-20 7:51 ` jakub at gcc dot gnu.org
2020-11-20 7:53 ` jakub at gcc dot gnu.org
2020-11-20 16:06 ` seurer at gcc dot gnu.org
2021-09-27 22:42 ` ldalessandro at gmail dot com
2021-09-27 22:46 ` 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-97911-4-hDdPuxrXMm@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).