Paul Goyette <p...@whooppee.com> wrote: > <...> > > # link npfctl/npfctl > /build/test/tools/x86_64/amd64/bin/x86_64--netbsd-gcc \ > --sysroot=/build/test/dest/amd64 -o npfctl \ > npfctl.o npf_var.o npf_data.o npf_ncgen.o npf_build.o \ > npf_extmod.o npf_disassemble.o npf_scan.o npf_parse.o \ > -lnpf -lprop -lcrypto -lutil -ly \ > -Wl,-dynamic-linker=/libexec/ld.elf_so \ > -Wl,-rpath,/lib -L=/lib > /lib/libcrypt.so.1: undefined reference to `__explicit_memset' > > Is it, for some reason, trying to use the host's installed copy of > libcrypt rather than the one that was built earlier in $DESTDIR? (I > notice that it uses "-lcrypto" in the Makefile, but the error message > refers to libcrypt - without the 'o'). > > So, > > 1. Will adding "-l crypt" to npfctl's Makefile fix this? > 2. If I do that, do I also need to add ${LIBCRYPT} to DPADD? > 3. Any other additional changes needed?
Seems like the same PR/47922, where joerg@ made a fix for ld(1). -- Mindaugas