libgrapheme

commit 3697387a0a5fcb53df0094d988496f7a681ae54c
parent 5ef98fdec958130a92aa40006ddd9daba36b4d12
Author: Laslo Hunhold <dev@frign.de>
Date:   Tue, 16 Aug 2022 17:43:07 +0200

Revert "Use ar(1)'s s-flag instead of invoking ranlib(1)"

After further discussion with Roberto on the mailing list, it makes
more sense to keep ranlib(1). There are good reasons why POSIX does not
define it, given it relies on the binary format. Specifying the s-flag
for ar(1) is thus very surprising, but should not be a reason not to use
ranlib(1).

This reverts commit 5fc87aedad86a8410a360ba718096e613ddf11f6.

Diffstat:
M
Makefile
 | 
3
++-
M
config.mk
 | 
1
+

2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
@@ -187,7 +187,8 @@ $(TEST):
 	$(CC) -c -o $@ $(CPPFLAGS) $(CFLAGS) $<
 
 libgrapheme.a: $(SRC:=.o)
-	$(AR) -rcs $@ $?
+	$(AR) -rc $@ $?
+	$(RANLIB) $@
 
 libgrapheme.so: $(SRC:=.o)
 	$(CC) -o $@ -shared $(SRC:=.o)
diff --git a/config.mk b/config.mk
@@ -17,3 +17,4 @@ LDFLAGS  = -s
 # tools
 CC = cc
 AR = ar
+RANLIB = ranlib