Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Hannes Domani <ssbssa@yahoo.de>
To: "gdb@gnu.org" <gdb@gnu.org>
Subject: Re: GDB 9.1 Fails to Build on Cygwin
Date: Wed, 25 Mar 2020 19:27:06 +0000 (UTC)	[thread overview]
Message-ID: <1133848898.4146549.1585164426040@mail.yahoo.com> (raw)
In-Reply-To: <CAF9ehCXPMSDM30EZynr223HR58K7kWzsh7H7+uLfm7E0oLPDFQ@mail.gmail.com>

 Am Mittwoch, 25. März 2020, 20:01:06 MEZ hat Joel Sherrill <joel@rtems.org> Folgendes geschrieben:

> Hi
>
> Over at RTEMS, we are seeing gdb 9.1 fail to build arm-eabi and fail with
> this:
>
> CXXLD  gdb.exe
> cp-support.o:/desk/b-arm-eabi-bin/gdb/../../gdb-9.1/gdb/cp-support.c:2212:(.text+0x1bf6):
> relocation truncated to fit: R_X86_64_PC32 against undefined symbol `TLS
> init function for thread_local_segv_handler'
> cp-support.o:/desk/b-arm-eabi-bin/gdb/../../gdb-9.1/gdb/cp-support.c:2212:(.text+0x1c00):
> 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
> make[2]: *** [Makefile:1908: gdb.exe] Error 1
> make[2]: Leaving directory '/desk/b-arm-eabi-bin/gdb'
> make[1]: *** [Makefile:9567: all-gdb] Error 2
> make[1]: Leaving directory '/desk/b-arm-eabi-bin'
> make: *** [Makefile:855: all] Error 2
>
> gdb 8.0.1 builds OK.
>
> Does anyone have any ideas how to solve this?

This looks very much like gcc bug 64697:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64697

And 8.0.1 didn't use thread_local yet (9.1 is the first version that uses it).


Regards
Hannes Domani


  reply	other threads:[~2020-03-25 19:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 19:00 Joel Sherrill
2020-03-25 19:27 ` Hannes Domani [this message]
2020-03-26 22:11   ` Jim Wilson
2020-03-26 22:23     ` Joel Sherrill
2020-03-26 22:45       ` Jim Wilson

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=1133848898.4146549.1585164426040@mail.yahoo.com \
    --to=ssbssa@yahoo.de \
    --cc=gdb@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