Follow-up Comment #1, sr #111196 (group libtool): Thank you for your bug report.
I was able to reproduce this issue, but I do not think it is something that
needs an update in libtool. Instead, you should execute a libtool clean
between subsequent builds, similarly to just removing the output archive.
$LIBTOOL --mode=compile --tag=CC $CC -c -o foo.lo $CPPFLAGS $CFLAGS -arch
x86_64 -arch arm64 foo.c
libtool: compile: gcc -c -Wall -g -O2 -arch x86_64 -arch arm64 foo.c
-fno-common -DPIC -o .libs/foo.o
libtool: compile: gcc -c -Wall -g -O2 -arch x86_64 -arch arm64 foo.c -o foo.o
>/dev/null 2>&1
$LIBTOOL --mode=link --tag=CC $CC -static $CPPFLAGS $CFLAGS -o libfoo.a
foo.lo
libtool: link: ar cr libfoo.a foo.o
libtool: link: ranlib libfoo.a
$LIBTOOL --mode=clean rm -f libfoo.a
libtool: clean: rm -f libfoo.a
libtool: clean: rmdir .libs >/dev/null 2>&1
$LIBTOOL --mode=compile --tag=CC $CC -c -o foo.lo $CPPFLAGS $CFLAGS -arch
x86_64 -arch arm64 foo.c
libtool: compile: gcc -c -Wall -g -O2 -arch x86_64 -arch arm64 foo.c
-fno-common -DPIC -o .libs/foo.o
libtool: compile: gcc -c -Wall -g -O2 -arch x86_64 -arch arm64 foo.c -o foo.o
>/dev/null 2>&1
$LIBTOOL --mode=link --tag=CC $CC -static $CPPFLAGS $CFLAGS -o libfoo.a
foo.lo
libtool: link: ar cr libfoo.a foo.o
libtool: link: ranlib libfoo.a
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?111196>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
