Tom,
> The main "problem" here is that ranlib(1) isn't a standardized tool, so there
> is no guarantee on what its behaviour will be or whether it exists at all.
> We assume it's there because it always has been or GNU and LLVM include it.
an option might be to wait until the bug report comes in
Hi,
On Fri, Jul 22, 2022 at 05:26:52PM +0200, Roberto E. Vargas Caballero wrote:
> Hi,
>
> On Wed, Jul 20, 2022 at 12:23:01PM +, Tom Schwindl wrote:
> > ranlib(1) is, in fact, legacy. It was used to create symbol tables for
> > archives
> > before ar(1) was able to do that by itself.
> > POS
