From: Christian Biesinger <cbiesinger@google.com>
To: joel@rtems.org, Tom Tromey <tom@tromey.com>
Cc: Reuben Thomas via Gdb <gdb@sourceware.org>
Subject: Re: Build Failure on Cygwin
Date: Mon, 19 Oct 2020 19:42:35 +0200 [thread overview]
Message-ID: <CAPTJ0XF8XLYh9e3eEhRsV6XoCLbT5PZ1nT0VfqLMLcAaWS-dmA@mail.gmail.com> (raw)
In-Reply-To: <CAF9ehCX0u6XBerx3GU2myhgJYzW6iL+LWKs8tEoxFOkt2hBGoA@mail.gmail.com>
On Mon, Oct 19, 2020 at 7:26 PM Joel Sherrill <joel@rtems.org> wrote:
> I am getting a build failure on Cygwin
>
> /home/jrs007/rtems-cron-6/rtems-source-builder/rtems/build/aarch64-rtems6-gdb-8a6e98c-x86_64-pc-cygwin-1/build/gdb/../../sourceware-mirror-binutils-gdb-8a6e98c/gdb/cp-support.c:1619:(.text+0x5502):
> relocation truncated to fit: R_X86_64_PC32 against undefined symbol `TLS
> init function for thread_local_segv_handler'
> /home/jrs007/rtems-cron-6/rtems-source-builder/rtems/build/aarch64-rtems6-gdb-8a6e98c-x86_64-pc-cygwin-1/build/gdb/../../sourceware-mirror-binutils-gdb-8a6e98c/gdb/cp-support.c:1619:(.text+0x551b):
> relocation truncated to fit: R_X86_64_PC32 against undefined symbol `TLS
> init function for thread_local_segv_handler'
> collect2: error: ld returned 1 exit status
I've seen this error on various toolchains. I believe it to be a gcc
bug; however, since it still seems to be an issue on some platforms,
maybe gdb should avoid using global (nonstatic) threadlocal
variables... (and instead abstract access to this variable through
getters/setters)
Christian
next prev parent reply other threads:[~2020-10-19 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 17:26 Joel Sherrill
2020-10-19 17:42 ` Christian Biesinger [this message]
2020-10-19 17:46 ` Hannes Domani
2020-10-19 19:33 ` Joel Sherrill
2020-10-19 23:03 ` Joel Sherrill
2020-10-20 11:39 ` Christian Biesinger
2020-10-20 13:35 ` Joel Sherrill
2020-10-20 18:23 ` Hannes Domani
2020-10-20 19:18 ` Joel Sherrill
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=CAPTJ0XF8XLYh9e3eEhRsV6XoCLbT5PZ1nT0VfqLMLcAaWS-dmA@mail.gmail.com \
--to=cbiesinger@google.com \
--cc=gdb@sourceware.org \
--cc=joel@rtems.org \
--cc=tom@tromey.com \
/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).