vagrant@Rock960:~/rkdeveloptool$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking whether make sets $(MAKE)... (cached) yes
checking whether ln -s works... yes
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for library containing iconv... none required
./configure: line 4482: syntax error near unexpected token `LIBUSB1,libusb-1.0'
./configure: line 4482: `PKG_CHECK_MODULES(LIBUSB1,libusb-1.0)'
Please enter some details about the bug/issue so we can promptly resolve it. URL: https://www.96boards.org/documentation/consumer/rock/installation/linux-mac-rkdeveloptool.md.html
Using an Ubuntu 18.04 host to build the
rkdeveloptool
I found the instructions don't work as I get this error when running./configure
:Demo using a clean bento/ubuntu-18.04 Vagrant VM ( https://vagrantup.com and
vagrant init bento/ubuntu-18.04
):I found this solution: https://github.com/nfc-tools/libnfc/issues/373#issuecomment-280785351
So I suggest adding
libglib2.0-dev
to the list of packages.