Log files in gllvm contain calls to clang compilation and linking commands. There are cases where a binary is built by compiling and then linking against an archive library. This library is built during the build process. An example of this is gzip. Here is the linking of gzip:
AUDIT:LINKING clang [-g -O2 -Wl,--as-needed -o gzip bits.o deflate.o gzip.o inflate.o trees.o unlzh.o unlzw.o unpack.o unzip.o util.o zip.o libver.a lib/libgzip.a]
lib/libgzip.a is built during the build of gzip by compiling a number of source files into object files. They are then archived into lib/libgzip.a. the log file does not capture this archive step. I think it should.
Log files in gllvm contain calls to clang compilation and linking commands. There are cases where a binary is built by compiling and then linking against an archive library. This library is built during the build process. An example of this is gzip. Here is the linking of gzip:
AUDIT:LINKING clang [-g -O2 -Wl,--as-needed -o gzip bits.o deflate.o gzip.o inflate.o trees.o unlzh.o unlzw.o unpack.o unzip.o util.o zip.o libver.a lib/libgzip.a]lib/libgzip.ais built during the build of gzip by compiling a number of source files into object files. They are then archived intolib/libgzip.a. the log file does not capture this archive step. I think it should.