On Fri, May 29, 2020 at 01:12:42PM -0600, Steve Williams wrote: > It applies patches and compiles clean. However, when I try to create a > package, it seems to want to include the libraries that I have in WANTLIB.
WANTLIB doesn't work by itself. It also requires LIB_DEPENDS/RUN_DEPENDS Basically, there are two complimentary mechanisms for dependencies BUILD/RUN/LIB _DEPENDS paths to other ports you need during build, run time, and for libraries WANTLIB the explicit libraries that are either in the base system, or reachable through LIB/RUN depends All port dependencies mechanisms will walk through the LIB/RUN depends tree and figure out what libraries are available for WANTLIB make port-lib-depends-check will look at your built port (in the fake dir) and tell you what libraries you should need in WANTLIB (by looking at ELF headers, mostly NEEDED stuff), so it's accurate for anything that doesn't load libraries using dlopen. *If* a library is found, but it can't be reached through the *DEPENDS tree, it will tell you that the library is NOT REACHABLE (most probably what you will see here). These days, LIB_DEPENDS is mostly a convenience for BUILD_DEPENDS+RUN_DEPENDS. It used to be that it was more complicated when we had non-shared architectures like vax... I'll admit the message from make package is not as useful as it could be... but port-wantlib-args is already fairly complicated as-is.
