On 1/16/25 03:32, Greg A. Woods wrote:
I've never ever been comfortable with not knowing all dependencies explicitly, including the transitive dependencies of intermediate libraries, at build time. The main program's build really should know all the dependencies its product(s) will have, not just the "front-line" ones.
...even if some programs need this, and failing to maintain the list of dependencies (including their ordering) does not always cause an error?
LIBKRB5_LDADD+= -lkrb5 -lcom_err \ -lhx509 -lcrypto -lasn1 \ -lwind -lheimbase -lcom_err -lroken \ -lcrypt -lutil LIBGSSAPI_LDADD+= -lgssapi -lheimntlm ${LIBKRB5_LDADD} I don't think this is a viable solution and I'm all for Taylor's suggestion.