On Wed, Oct 09, 2013 at 21:08:09 -0700, Paul Goyette wrote:
I then attempt to run a 'build.sh build' using
./build.sh -T /build/test/tools/x86_64/amd64 \
-D /build/test/dest/amd64 \
-O /build/test/obj/amd64 \
-R /build/test/release \
On Thu, Oct 10, 2013 at 05:27:56 -0700, Paul Goyette wrote:
On Thu, 10 Oct 2013, Valery Ushakov wrote:
On Wed, Oct 09, 2013 at 21:08:09 -0700, Paul Goyette wrote:
/build/test/tools/x86_64/amd64/bin/x86_64--netbsd-gcc\
--sysroot=/build/test/dest/amd64 -o npfctl \
On Thu, Oct 10, 2013 at 06:40:51PM +0400, Valery Ushakov wrote:
/build/test/tools/x86_64/amd64/bin/x86_64--netbsd-gcc\
--sysroot=/build/test/dest/amd64 -o npfctl \
Go to the objdir and run that command (without -lcrypt) with
-Wl,--verbose - you should see something like
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
On Thu, 10 Oct 2013, Mindaugas Rasiukevicius wrote:
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').
