https://sourceware.org/bugzilla/show_bug.cgi?id=25120
--- Comment #12 from Nick Alcock ---
Thanks! I already have that locally -- I really should finish testing and
submit everything.
Simply removing __thread won't do, unfortunately: it makes libctf even less
threadsafe than it already is, and
https://sourceware.org/bugzilla/show_bug.cgi?id=25120
Michael Forney changed:
What|Removed |Added
Attachment #12084|0 |1
is obsolete|
https://sourceware.org/bugzilla/show_bug.cgi?id=25120
--- Comment #10 from Michael Forney ---
I ran into issues 1 (__thread) and 2 (__libctf_*_) when building
binutils-2.33.1 with my C compiler (https://git.sr.ht/~mcf/cproc).
I found this issue when I went to submit a patch for issue 2, so I
https://sourceware.org/bugzilla/show_bug.cgi?id=25120
Michael Forney changed:
What|Removed |Added
CC||mforney at mforney dot org
---
https://sourceware.org/bugzilla/show_bug.cgi?id=25120
--- Comment #8 from Nick Alcock ---
Nice diagnosis! Looks like there are some bugs in busybox and tcc to fix. I
agree that the first three things you reported are bugs, and I'll fix them once
I get a spare moment. Thanks for the report!
--
https://sourceware.org/bugzilla/show_bug.cgi?id=25120
--- Comment #7 from Harald van Dijk ---
(In reply to Harald van Dijk from comment #6)
> This is not compatible with how libbfd.a is created,
> where ar is invoked multiple times, so if I use this instead, readelf does
> build, but nothing
https://sourceware.org/bugzilla/show_bug.cgi?id=25120
--- Comment #6 from Harald van Dijk ---
(In reply to Harald van Dijk from comment #5)
> (In reply to Nick Alcock from comment #4)
> > I'll try to get tcc working in a bit, but in the absence of that you could
> > try to figure out which
https://sourceware.org/bugzilla/show_bug.cgi?id=25120
--- Comment #5 from Harald van Dijk ---
(In reply to Nick Alcock from comment #4)
> The C compiler shouldn't affect anything here: the linker in use is what
> matters.
tcc has its own built-in linker.
> I'll try to get tcc working in a bit,
https://sourceware.org/bugzilla/show_bug.cgi?id=25120
--- Comment #4 from Nick Alcock ---
The C compiler shouldn't affect anything here: the linker in use is what
matters.
I'll try to get tcc working in a bit, but in the absence of that you could try
to figure out which symbol in ctf-open-bfd.c
https://sourceware.org/bugzilla/show_bug.cgi?id=25120
--- Comment #3 from Harald van Dijk ---
(In reply to Nix from comment #1)
> 4: This is very strange. In 2.33, readelf carefully calls only .o files that
> do not cite BFD functions, even indirectly, so ctf-open-bfd.o is never
> pulled in and
https://sourceware.org/bugzilla/show_bug.cgi?id=25120
--- Comment #2 from Nick Alcock ---
(For the avoidance of doubt: the commenter above was me, logged in under the
wrong bugzilla account.)
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=25120
Nick Alcock changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://sourceware.org/bugzilla/show_bug.cgi?id=25120
Nick Alcock changed:
What|Removed |Added
Assignee|unassigned at sourceware dot org |nick.alcock at oracle
dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=25120
Nick Alcock changed:
What|Removed |Added
CC|nix at esperi dot org.uk |nick.alcock at oracle
dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=25120
Nix changed:
What|Removed |Added
CC||nix at esperi dot org.uk
--- Comment #1 from
15 matches
Mail list logo
