https://sourceware.org/bugzilla/show_bug.cgi?id=18430
Cary Coutant <ccoutant at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|ccoutant at gmail dot com |shenhan at google dot
com
--- Comment #2 from Cary Coutant <ccoutant at gmail dot com> ---
A tarball containing all the inputs to the link, including the @-file would
help. (You can add the -Wl,-t option to the c++ command to get a list of all
the files that the linker reads.)
If you also add the -v option to the c++ command, it'll show the actual linker
command (probably 'collect2'). That would also be helpful.
Are you using the --warn-unresolved-symbols option? It looks like this might be
a reference to an unresolved TLS symbol. Alternatively, it could be a TLS
relocation that refers to a non-TLS symbol, or a TLS symbol in a non-TLS
section.
The assertion you hit indicates that gold saw a TLS relocation but hadn't
created a TLS segment yet. Gold will create a TLS segment whenever it sees a
TLS section in an input file (i.e., a section with SHF_TLS set), or when it has
any TLS common symbols.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils
