[Bug binutils/25120] Portability issues in binutils 2.33 due to libctf

[harald at gigawatt dot nl]

https://sourceware.org/bugzilla/show_bug.cgi?id=25120

--- Comment #6 from Harald van Dijk <harald at gigawatt dot nl> ---
(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 symbol in ctf-open-bfd.c is at fault (or if it's all
> > of them).
> 
> I'll take a look.

Oh this is annoying, it depends on the ar being used. On my uclibc-ng system,
the ar used for building binutils is busybox ar (with a wrapper script to
accept the right options). busybox ar creates archives that do not contain a
"/" entry. When that is missing, tcc just links the whole archive.

tcc comes with a built-in archiver (tcc -ar) which does not have this problem
and can build readelf successfully. It does, however, have a different problem:
tcc -ar rc lib.a objs... overwrites lib.a. It always creates a new archive.
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 else.

I think these are bugs in busybox ar and tcc -ar. It would be nice to work
around them, but it is not really a bug in binutils.

-- 
You are receiving this mail because:
You are on the CC list for the bug.