https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111033
Bug ID: 111033
Summary: libcody build does not use AR_FLAGS
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: skunk at iskunk dot org
Target Milestone: ---
I am working on getting a reproducible GCC build. This includes passing the "D"
option to ar(1) to avoid non-deterministic static library outputs.
In bootstrapping 13.2.0, I noticed that libcody.a was not being generated
consistently. The libcody makefile has the following:
AR := @AR@
...
$(AR) -cr $@ $^
For comparison, in the rest of the GCC tree, you typically see
AR = @AR@
AR_FLAGS = rc
...
$(AR) $(AR_FLAGS) libfoo.a ...
and AR_FLAGS is the natural place to add additional flags. An AR_FLAGS variable
should thus likewise be added to the libcody makefile.
(ARFLAGS is also used; I am not entirely sure which form is favored.)
Beyond addressing this small inconsistency, it would be good to see the GCC
build itself check whether ar(1) supports the "D" flag, and add it
automatically if so.
