Syntax error near unexpected token libusb

Hi, When i do ./configure to install lib-nfc 1.7.1 i have this error: checking which drivers to build... acr122_usb checking for documentation request... no ./configure: line 14026: syntax error ne...

@Azef1

Hi,

When i do ./configure to install lib-nfc 1.7.1 i have this error:

checking which drivers to build... acr122_usb
checking for documentation request... no
./configure: line 14026: syntax error near unexpected token `libusb,'
./configure: line 14026: `        PKG_CHECK_MODULES(libusb, libusb, HAVE_LIBUSB=1, HAVE_LIBUSB=0)'

So, i did apt-get install libusb-dev

Reading package lists... Done
Building dependency tree       
Reading state information... Done
libusb-dev is already the newest version (2:0.1.12-30).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

But i always have the same error when i do ./configure

Could-you help me ?

My NFC reader is ACR122U and i work on kali linux

@BuptPeter

mayby you can try use:
autoconfig -vis
(you have to install autoconf at first.)

@doegox

You got the error

./configure: line 14026: syntax error near unexpected token `libusb,'
./configure: line 14026: `        PKG_CHECK_MODULES(libusb, libusb, HAVE_LIBUSB=1, HAVE_LIBUSB=0)'

because you’re missing libglib2.0-dev. Install it and try again:

apt-get install libglib2.0-dev
autoreconf -vis
./configure
make
eamirgh, abhas, TerjeBruoygard, omaraflak, ajurcevic, meermanr, NeverBehave, bandakkalokka, PlastMan420, ticpu, and 2 more reacted with thumbs up emoji

@smortex

Closing as @doegox gave a solution. Please reopen if this does not fix your problem.

joaomorenorf

added a commit
to joaomorenorf/blog
that referenced
this issue

Mar 17, 2018

@joaomorenorf

@Krazubu

I’m getting the same error with 1.5.1, however doing

apt-get install libglib2.0-dev
autoreconf -vis 

does not help

EDIT : OK, after pulling my hair out for hours, I figured this happened because of missing «pkg-config» package.
On a side note, 1.5.1 won’t compile on recent Linux (Ubuntu 16) with libusb 1.0 nor 0.1, you must use libusb-compat.

sergeygrigorev

added a commit
to sergeygrigorev/zigbee2mqtt.io
that referenced
this issue

Oct 14, 2020

@sergeygrigorev

Koenkk

pushed a commit
to Koenkk/zigbee2mqtt.io
that referenced
this issue

Oct 14, 2020

@sergeygrigorev

@symdeb

From clean Ubuntu I had to install
build-essentials
autoconf
libusb-1.0
libudev-dev
libglib2.0-dev

Содержание

  1. Arch Linux
  2. #1 2019-12-18 17:14:31
  3. [SOLVED] syntax error near unexpected token `LIBUSB,’
  4. #2 2019-12-18 18:09:57
  5. Re: [SOLVED] syntax error near unexpected token `LIBUSB,’
  6. #3 2019-12-18 18:17:11
  7. Re: [SOLVED] syntax error near unexpected token `LIBUSB,’
  8. #4 2019-12-18 18:24:53
  9. Re: [SOLVED] syntax error near unexpected token `LIBUSB,’
  10. #5 2019-12-18 18:29:26
  11. Re: [SOLVED] syntax error near unexpected token `LIBUSB,’
  12. Arch Linux
  13. #1 2009-08-06 15:18:34
  14. unexpected token, autoconf error?
  15. #2 2009-08-06 23:31:36
  16. Re: unexpected token, autoconf error?
  17. #3 2009-08-08 00:00:04
  18. Re: unexpected token, autoconf error?
  19. #4 2009-08-13 15:37:06
  20. Re: unexpected token, autoconf error?
  21. #5 2009-08-14 01:08:52
  22. Re: unexpected token, autoconf error?
  23. #6 2009-08-14 01:49:13
  24. Re: unexpected token, autoconf error?
  25. #7 2009-08-14 14:46:49
  26. Re: unexpected token, autoconf error?
  27. Syntax error near unexpected token «libusbmuxd» #89
  28. Comments
  29. Footer
  30. PKG_CHECK_MODULES USB unexpected token #83
  31. Comments

Arch Linux

You are not logged in.

#1 2019-12-18 17:14:31

[SOLVED] syntax error near unexpected token `LIBUSB,’

I have been trying to install a program called QCMA (https://aur.archlinux.org/packages/qcma/) from source but have been getting this error when trying to install the following dependency (https://aur.archlinux.org/packages/libvitamtp/). I can see that I also have the correct version of libusb installed according to pacman.

checking for the common suffixes of directories in the library search path. lib,lib
checking for iconv. yes
checking for working iconv. yes
checking for iconv declaration.
extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft);
./configure: line 10181: PKG_PROG_PKG_CONFIG: command not found
checking For MinGW32. no
configure: API documentation will not be generated
./configure: line 10297: syntax error near unexpected token `LIBUSB,’
./configure: line 10297: ` PKG_CHECK_MODULES(LIBUSB, libusb-1.0)’

$ pacman -Ss libusb
core/libusb 1.0.23-2 [installed]
Library that provides generic access to USB devices

my kernel is: x86_64 Linux 5.4.2-1

Last edited by singha95 (2019-12-18 18:41:35)

#2 2019-12-18 18:09:57

Re: [SOLVED] syntax error near unexpected token `LIBUSB,’

#3 2019-12-18 18:17:11

Re: [SOLVED] syntax error near unexpected token `LIBUSB,’

I already have the base-devel group installed on my machine:

$ pacman -Ss base-devel
core/autoconf 2.69-6 (base-devel) [installed]
A GNU tool for automatically configuring source code
core/automake 1.16.1-2 (base-devel) [installed]
A GNU tool for automatically creating Makefiles
core/binutils 2.33.1-2 (base-devel) [installed]
A set of programs to assemble and manipulate binary and object files
core/bison 3.4.2-2 (base-devel) [installed]
The GNU general-purpose parser generator
core/fakeroot 1.24-2 (base-devel) [installed]
Tool for simulating superuser privileges
core/file 5.37-5 (base-devel) [installed]
File type identification utility
core/findutils 4.7.0-2 (base-devel) [installed]
GNU utilities to locate files
core/flex 2.6.4-3 (base-devel) [installed]
A tool for generating text-scanning programs
core/gawk 5.0.1-2 (base-devel) [installed]
GNU version of awk
core/gcc 9.2.0-4 (base-devel) [installed]
The GNU Compiler Collection — C and C++ frontends
core/gettext 0.20.1-3 (base-devel) [installed]
GNU internationalization library
core/grep 3.3-3 (base-devel) [installed]
A string search utility
core/groff 1.22.4-2 (base-devel) [installed]
GNU troff text-formatting system
core/gzip 1.10-3 (base-devel) [installed]
GNU compression utility
core/libtool 2.4.6+42+gb88cebd5-8 (base-devel) [installed]
A generic library support script
core/m4 1.4.18-3 (base-devel) [installed]
The GNU macro processor
core/make 4.2.1-4 (base-devel) [installed]
GNU make utility to maintain groups of programs
core/pacman 5.2.1-2 (base-devel) [installed]
A library-based package manager with dependency support
core/patch 2.7.6-8 (base-devel) [installed]
A utility to apply patch files to original sources
core/pkgconf 1.6.3-3 (base-devel) [installed]
Package compiler and linker metadata toolkit
core/sed 4.7-3 (base-devel) [installed]
GNU stream editor
core/sudo 1.8.29-1 (base-devel) [installed]
Give certain users the ability to run some commands as root
core/texinfo 6.7-2 (base-devel) [installed]
GNU documentation system for on-line information and printed output
core/which 2.21-5 (base-devel) [installed]
A utility to show the full path of commands

#4 2019-12-18 18:24:53

Re: [SOLVED] syntax error near unexpected token `LIBUSB,’

Please post the full output for the build in code tags. It build in a clean chroot on this system

#5 2019-12-18 18:29:26

Re: [SOLVED] syntax error near unexpected token `LIBUSB,’

I found my mistake. I was using the developers github instructions and running the .configure file manually. Pulling the AUR repo and running the makepkg -si command works. Marking as resolved.

Last edited by singha95 (2019-12-18 18:29:46)

Источник

Arch Linux

You are not logged in.

#1 2009-08-06 15:18:34

unexpected token, autoconf error?

I tried to compile the software ‘Barry’ (for Blackberry) and encountered a problem, the info is like:

the line 15301 related part of in file configure is like this

I tried to get some info in the web, is it an autoconf error?
http://www.nabble.com/darwin-patches-td20166331.html

but I don’t know what the problem.

I don’t know whether it is proper to post the problem here.

Last edited by felonwan (2009-08-06 15:23:58)

#2 2009-08-06 23:31:36

Re: unexpected token, autoconf error?

do you have libusb installed?

#3 2009-08-08 00:00:04

Re: unexpected token, autoconf error?

Which version of barry did you try to install, the git version or the simple ?

Both of them works by me from aur. Did you try it so, or just manually ?

#4 2009-08-13 15:37:06

Re: unexpected token, autoconf error?

Which version of barry did you try to install, the git version or the simple ?

Both of them works by me from aur. Did you try it so, or just manually ?

I tried to install it manually, because I didn’t know it can be installed from aur and how to then.
I’ll try.

Last edited by felonwan (2009-08-13 16:10:35)

#5 2009-08-14 01:08:52

Re: unexpected token, autoconf error?

Which version of barry did you try to install, the git version or the simple ?

Both of them works by me from aur. Did you try it so, or just manually ?

I’ve tried to install barry and barry-git from aur, the laster is OK, but the former encountered such err info:

.
g++ -DHAVE_CONFIG_H -I.. -ansi -Wall -fno-strict-aliasing -g -D__BARRY_HAVE_GCCVISIBILITY__ -fvisibility=hidden -march=i686 -mtune=generic -O2 -pipe -MT base64.lo -MD -MP -MF .deps/base64.Tpo -c base64.cc -fPIC -DPIC -o .libs/base64.o
base64.cc: In member function ‘int base64_input::operator()()’:
base64.cc:41: error: ‘EOF’ was not declared in this scope
base64.cc: In function ‘bool encode(base64_input&, base64_output&)’:
base64.cc:99: error: ‘EOF’ was not declared in this scope
base64.cc: In function ‘int insig(base64_input&)’:
base64.cc:138: error: ‘EOF’ was not declared in this scope
base64.cc: In function ‘bool decode(base64_input&, base64_output&)’:
base64.cc:174: error: ‘EOF’ was not declared in this scope
make[2]: *** [base64.lo] Error 1
make[2]: Leaving directory `/tmp/yaourt-tmp-root/aur-barry/barry/src/barry-0.14/src’
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/yaourt-tmp-root/aur-barry/barry/src/barry-0.14′
make: *** [all] Error 2
==> ERROR: Build Failed.
Aborting.
Error: Makepkg was unable to build barry package.
.

what’s the problem?

#6 2009-08-14 01:49:13

Re: unexpected token, autoconf error?

it need to be patched to build with the latest gcc.

#7 2009-08-14 14:46:49

Re: unexpected token, autoconf error?

Which version of barry did you try to install, the git version or the simple ?

Both of them works by me from aur. Did you try it so, or just manually ?

I’ve tried to install barry and barry-git from aur, the laster is OK, but the former encountered such err info:

.
g++ -DHAVE_CONFIG_H -I.. -ansi -Wall -fno-strict-aliasing -g -D__BARRY_HAVE_GCCVISIBILITY__ -fvisibility=hidden -march=i686 -mtune=generic -O2 -pipe -MT base64.lo -MD -MP -MF .deps/base64.Tpo -c base64.cc -fPIC -DPIC -o .libs/base64.o
base64.cc: In member function ‘int base64_input::operator()()’:
base64.cc:41: error: ‘EOF’ was not declared in this scope
base64.cc: In function ‘bool encode(base64_input&, base64_output&)’:
base64.cc:99: error: ‘EOF’ was not declared in this scope
base64.cc: In function ‘int insig(base64_input&)’:
base64.cc:138: error: ‘EOF’ was not declared in this scope
base64.cc: In function ‘bool decode(base64_input&, base64_output&)’:
base64.cc:174: error: ‘EOF’ was not declared in this scope
make[2]: *** [base64.lo] Error 1
make[2]: Leaving directory `/tmp/yaourt-tmp-root/aur-barry/barry/src/barry-0.14/src’
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/yaourt-tmp-root/aur-barry/barry/src/barry-0.14′
make: *** [all] Error 2
==> ERROR: Build Failed.
Aborting.
Error: Makepkg was unable to build barry package.
.

what’s the problem?

Don’t forget to kick the AUR maintainer/submitter to fix the issue

Источник

Syntax error near unexpected token «libusbmuxd» #89

Hi I am getting this error:

  1. brew install —HEAD libimobiledevice (Returning error and suggestion to «Brew Link libimobiledevice»)
  2. Brew Link libimobiledevice (returning error /bin is not writable)
  3. brew install ideviceinstaller ( Syntax error near unexpected token «libusbmuxd» )

Error: PKG_CHECK_MODULES(libusbmuxd, libusbmuxd >= $LIBUSBMUXD_VERSION)

The text was updated successfully, but these errors were encountered:

If I try to install using brew, I get the same error. If I simply download the latest from master and run ./autogen.sh , I get

I solved the issues I was seeing by running brew doctor . The specific issue that I was facing was that some folders had the wrong owner. The issue is described here — it might be the same for others landing here or it might be something else. Run brew doctor and see what the doctor has to say 😄

I have this error while compiling on Debian 9.4

P.S. Fixed with sudo apt install libimobiledevice-dev libplist++

thank you dear
God bless you

@iqbalhadi: what does God have to do with this?

checking how to hardcode library paths into programs. immediate
./configure: line 16050: syntax error near unexpected token libusbmuxd,’ ./configure: line 16050: PKG_CHECK_MODULES(libusbmuxd, libusbmuxd >= $LIBUSBMUXD_VERSION)’

In some cases it helps having the pkg-config package installed.

sudo apt install pkg-config

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

PKG_CHECK_MODULES USB unexpected token #83

I installed this a month ago on OSX and it went fine, I had to reinstall osx and now I am running into problems.

./configure: line 4781: syntax error near unexpected token USB,’ ./configure: line 4781: PKG_CHECK_MODULES(USB, libusb-1.0 >= 1.0.0,,’

I already installed libusb:

$ pkg-config —libs libusb
-L/usr/local/lib -lusb

$ pkg-config —libs libusb-1.0
-L/usr/local/lib -lusb-1.0

if I comment out the line 4781 from configure which causes the problem then it creates the make file but the makefile doesn’t Include or link correctly.

I can compile it by adding -lusb-1.0 to the gcc command (also added -I/usr/local/include/libusb to the makefile)

gcc -g -O2 -o st-util gdbserver/st_util-gdb-remote.o gdbserver/st_util-gdb-server.o mingw/st_util-mingw.o libstlink.a -lusb-1.0

Any ideas why I don’t have this USB token?
What should it be?

The text was updated successfully, but these errors were encountered:

can we remove autotools now? It’s causing more problems.

It seems the same trouble I had on OSX using homebrew.
In my case, it works well after adding a line «/usr/local/share/aclocal» in /usr/share/aclocal/dirlist file.

same problem here on Arch linux x86_64, gcc4.7 and autoconf 2.69.
How can i solve?
tomorrow i’ll try fall back to autoconf 2.13.

I’m having this issue today. I’ve read that this issue can occur when your pkg.m4 file isn’t in some sane directory. It will cause the aclocal.m4 file to not contain the PKG_CHECK_MODULES macro. This is true for me. by modifying the autogen.sh file to execute

aclocal —force -I /opt/local/share/aclocal

after the autoreconf line, i find the PKG_CHECK_MODULES macro in the generated aclocal.m4 file. Unfortunate it does not resolve my issue.

resolved my issue by adding:

ACLOCAL_AMFLAGS = -I /opt/local/share/aclocal

I can confirm that adding

ACLOCAL_AMFLAGS = -I /opt/local/share/aclocal

to Makefile.am made ./configure run successfully on osx Lion, whereas before it would fail with the same PCK_CHECK_MODULES error.

(ubuntu linux)
Anyone still experiencing this I did
sudo apt-get install pkg-config
and it worked. Thanks to https://twitter.com/KenichiHidai for pointing me in the right direction.

installing libusb-1.0-0-dev helps me on Ubuntu 12

aclocal —force -I /opt/local/share/aclocal

once was enough for me.
My config is

  • Mac OS X Mountain Lion 10.8.2
  • automake 1.13.1, autoconf 2.69 from MacPorts

here is what worked on my MacAir (10.7.5).

  1. Add ACLOCAL_AMFLAGS = -I /opt/local/share/aclocal to Makefile.am
  2. sudo port install libftdi0
  3. sudo port install libusb
  4. ./autogen.sh
  5. ./configure
  6. make

Tested with st-flash and all worked smoothly.

PS: On my MacPro (10.7.5) step #2 was not necessary.

ACLOCAL_FLAGS=»-I /usr/share/aclocal» ./autogen.sh works for me!
I find my pkg.m4 here /usr/share/aclocal.

Had the same issue — finally solved it the following way — from comments I figured out that configure script cannot find pkg.mp4 pkg-config file.
Couldn’t find it either in /opt/local/share/aclocal nor in /usr/share/aclocal but used the following command:
brew list pkg-config
which outputted — /usr/local/Cellar/pkg-config/0.28/share/aclocal/pkg.m4
added
ACLOCAL_AMFLAGS = -I /usr/local/Cellar/pkg-config/0.28/share/aclocal/
to Makefile.am and it worked fine.

OS: Mac OSX 10.7.5 + homebrew

Thanks everyone for the tips!

I’m unfortunately having similar problems to all above, but none of the options have solved it. I’ve tried with macports and with homebrew. I get this error after ./configure:
./configure: line 4422: syntax error near unexpected token USB,’ ./configure: line 4422: PKG_CHECK_MODULES(USB, libusb-1.0 >= 1.0.0,,’

«by modifying the autogen.sh file to execute
aclocal —force -I /opt/local/share/aclocal
.
resolved my issue by adding:
ACLOCAL_AMFLAGS = -I /opt/local/share/aclocal
to Makefile.am»

«executing
aclocal —force -I /opt/local/share/aclocal
once was enough for me. «

«Had the same issue — finally solved it the following way — from comments I figured out that configure script cannot find pkg.mp4 pkg-config file.
Couldn’t find it either in /opt/local/share/aclocal nor in /usr/share/aclocal but used the following command:
brew list pkg-config
which outputted — /usr/local/Cellar/pkg-config/0.28/share/aclocal/pkg.m4
added
ACLOCAL_AMFLAGS = -I /usr/local/Cellar/pkg-config/0.28/share/aclocal/
to Makefile.am and it worked fine.»

brew list pkg-config gives me «Error: No such keg: /usr/local/Cellar/pkg-config»

and this one
«here is what worked on my MacAir (10.7.5).

Add ACLOCAL_AMFLAGS = -I /opt/local/share/aclocal to Makefile.am
sudo port install libftdi0
sudo port install libusb
./autogen.sh
./configure
make
Tested with st-flash and all worked smoothly.»

with no change. does anyone have any idea what’s going on here? Thanks in advance!

Источник

Please post the full output for the build in code tags.  It build in a clean chroot on this system

extra-x86_64-build 
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community               4.8 MiB  5.92 MiB/s 00:01 [######################] 100%
:: Starting full system upgrade...
 there is nothing to do
==> Building in chroot for [extra] (x86_64)...
==> Synchronizing chroot copy [/var/lib/archbuild/extra-x86_64/root] -> [testuser]...done
==> Making package: libvitamtp 2.5.9-1 (Wed Dec 18 18:22:26 2019)
==> Retrieving sources...
  -> Found vitamtp-2.5.9.tar.gz
  -> Found libvitamtp.install
==> Validating source files with sha256sums...
    vitamtp-2.5.9.tar.gz ... Passed
    libvitamtp.install ... Passed
==> Making package: libvitamtp 2.5.9-1 (Wed 18 Dec 2019 06:22:30 PM)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found vitamtp-2.5.9.tar.gz
  -> Found libvitamtp.install
==> WARNING: Skipping all source file integrity checks.
==> Extracting sources...
  -> Extracting vitamtp-2.5.9.tar.gz with bsdtar
==> Starting build()...
Removing libtool cruft
Running libtoolize
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
Removing aclocal cruft
Running aclocal -I ./m4 
Removing autoheader cruft
Running autoheader
Removing automake cruft
Running automake
configure.ac:12: installing './compile'
configure.ac:13: installing './config.guess'
configure.ac:13: installing './config.sub'
configure.ac:7: installing './install-sh'
configure.ac:7: installing './missing'
src/Makefile.am: installing './depcomp'
Removing autoconf cruft
Running autoconf
Finished!
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
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 whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... gcc3
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %sn
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... no
checking if : is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for ld... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking for shared library run path origin... done
checking 32-bit host C ABI... no
checking for the common suffixes of directories in the library search path... lib,lib
checking for iconv... yes
checking for working iconv... yes
checking for iconv declaration... 
         extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft);
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking For MinGW32... no
configure: API documentation will not be generated
checking for LIBUSB... yes
checking arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking sys/select.h usability... yes
checking sys/select.h presence... yes
checking for sys/select.h... yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking for select... yes
checking for socket... yes
checking for socketpair... yes
checking for XML... yes
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... no
checking whether pthreads work with -Kthread... no
checking whether pthreads work with -kthread... no
checking for the pthreads library -llthread... no
checking whether pthreads work with -pthread... yes
checking whether pthreads work with -pthreads... no
checking whether pthreads work with -mthreads... no
checking for the pthreads library -lpthread... yes
checking whether pthreads work with --thread-safe... no
checking whether pthreads work with -mt... no
checking for the pthreads library -lpthreadGC2... no
checking errno.h usability... yes
checking errno.h presence... yes
checking for errno.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking iconv.h usability... yes
checking iconv.h presence... yes
checking for iconv.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking for memory.h... (cached) yes
checking signal.h usability... yes
checking signal.h presence... yes
checking for signal.h... yes
checking stdarg.h usability... yes
checking stdarg.h presence... yes
checking for stdarg.h... yes
checking stddef.h usability... yes
checking stddef.h presence... yes
checking for stddef.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking time.h usability... yes
checking time.h presence... yes
checking for time.h... yes
checking for unistd.h... (cached) yes
checking for inline... inline
checking for int16_t... yes
checking for int32_t... yes
checking for int64_t... yes
checking for int8_t... yes
checking for size_t... yes
checking for ssize_t... yes
checking for uint16_t... yes
checking for uint32_t... yes
checking for uint64_t... yes
checking for uint8_t... yes
checking for ptrdiff_t... yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for working memcmp... yes
checking whether time.h and sys/time.h may both be included... yes
checking for sys/time.h... yes
checking for unistd.h... (cached) yes
checking for alarm... yes
checking for working mktime... yes
checking whether lstat correctly handles trailing slash... yes
checking whether stat accepts an empty string... no
checking for stdlib.h... (cached) yes
checking for GNU libc compatible realloc... yes
checking for getcwd... yes
checking for memset... yes
checking for mkdir... yes
checking for strchr... yes
checking for strcspn... yes
checking for strdup... yes
checking for strrchr... yes
checking for strstr... yes
checking for strtol... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking for uint8_t in stdint.h... yes
checking whether byte ordering is bigendian... no
checking for le32toh in machine/endian.h... no
checking for ntohl in arpa/inet.h... yes
checking for swap32 in machine/endian.h... no
checking for bswap_32 in byteswap.h... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating doc/Doxyfile
config.status: creating Makefile
config.status: creating doc/Makefile
config.status: creating src/Makefile
config.status: creating libvitamtp.pc
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
make  all-recursive
make[1]: Entering directory '/build/libvitamtp/src/vitamtp-2.5.9'
Making all in src
make[2]: Entering directory '/build/libvitamtp/src/vitamtp-2.5.9/src'
/bin/sh ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..   -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Wno-unused-parameter -Wno-parentheses -I/usr/include/libxml2  -I/usr/include/libusb-1.0  -DPTP_USB_SUPPORT -DPTP_IP_SUPPORT -pthread  -D_REENTRANT -D_THREAD_SAFE -D_POSIX_PTHREAD_SEMANTICS  -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -MT libvitamtp_la-datautils.lo -MD -MP -MF .deps/libvitamtp_la-datautils.Tpo -c -o libvitamtp_la-datautils.lo `test -f 'datautils.c' || echo './'`datautils.c
/bin/sh ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..   -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Wno-unused-parameter -Wno-parentheses -I/usr/include/libxml2  -I/usr/include/libusb-1.0  -DPTP_USB_SUPPORT -DPTP_IP_SUPPORT -pthread  -D_REENTRANT -D_THREAD_SAFE -D_POSIX_PTHREAD_SEMANTICS  -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -MT libvitamtp_la-device.lo -MD -MP -MF .deps/libvitamtp_la-device.Tpo -c -o libvitamtp_la-device.lo `test -f 'device.c' || echo './'`device.c
/bin/sh ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..   -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Wno-unused-parameter -Wno-parentheses -I/usr/include/libxml2  -I/usr/include/libusb-1.0  -DPTP_USB_SUPPORT -DPTP_IP_SUPPORT -pthread  -D_REENTRANT -D_THREAD_SAFE -D_POSIX_PTHREAD_SEMANTICS  -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -MT libvitamtp_la-ptp.lo -MD -MP -MF .deps/libvitamtp_la-ptp.Tpo -c -o libvitamtp_la-ptp.lo `test -f 'ptp.c' || echo './'`ptp.c
/bin/sh ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..   -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Wno-unused-parameter -Wno-parentheses -I/usr/include/libxml2  -I/usr/include/libusb-1.0  -DPTP_USB_SUPPORT -DPTP_IP_SUPPORT -pthread  -D_REENTRANT -D_THREAD_SAFE -D_POSIX_PTHREAD_SEMANTICS  -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -MT libvitamtp_la-usb.lo -MD -MP -MF .deps/libvitamtp_la-usb.Tpo -c -o libvitamtp_la-usb.lo `test -f 'usb.c' || echo './'`usb.c
/bin/sh ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..   -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Wno-unused-parameter -Wno-parentheses -I/usr/include/libxml2  -I/usr/include/libusb-1.0  -DPTP_USB_SUPPORT -DPTP_IP_SUPPORT -pthread  -D_REENTRANT -D_THREAD_SAFE -D_POSIX_PTHREAD_SEMANTICS  -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -MT libvitamtp_la-vitamtp.lo -MD -MP -MF .deps/libvitamtp_la-vitamtp.Tpo -c -o libvitamtp_la-vitamtp.lo `test -f 'vitamtp.c' || echo './'`vitamtp.c
/bin/sh ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..   -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Wno-unused-parameter -Wno-parentheses -I/usr/include/libxml2  -I/usr/include/libusb-1.0  -DPTP_USB_SUPPORT -DPTP_IP_SUPPORT -pthread  -D_REENTRANT -D_THREAD_SAFE -D_POSIX_PTHREAD_SEMANTICS  -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -MT libvitamtp_la-wireless.lo -MD -MP -MF .deps/libvitamtp_la-wireless.Tpo -c -o libvitamtp_la-wireless.lo `test -f 'wireless.c' || echo './'`wireless.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Wno-unused-parameter -Wno-parentheses -I/usr/include/libxml2 -I/usr/include/libusb-1.0 -DPTP_USB_SUPPORT -DPTP_IP_SUPPORT -pthread -D_REENTRANT -D_THREAD_SAFE -D_POSIX_PTHREAD_SEMANTICS -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -MT libvitamtp_la-ptp.lo -MD -MP -MF .deps/libvitamtp_la-ptp.Tpo -c ptp.c  -fPIC -DPIC -o .libs/libvitamtp_la-ptp.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Wno-unused-parameter -Wno-parentheses -I/usr/include/libxml2 -I/usr/include/libusb-1.0 -DPTP_USB_SUPPORT -DPTP_IP_SUPPORT -pthread -D_REENTRANT -D_THREAD_SAFE -D_POSIX_PTHREAD_SEMANTICS -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -MT libvitamtp_la-wireless.lo -MD -MP -MF .deps/libvitamtp_la-wireless.Tpo -c wireless.c  -fPIC -DPIC -o .libs/libvitamtp_la-wireless.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Wno-unused-parameter -Wno-parentheses -I/usr/include/libxml2 -I/usr/include/libusb-1.0 -DPTP_USB_SUPPORT -DPTP_IP_SUPPORT -pthread -D_REENTRANT -D_THREAD_SAFE -D_POSIX_PTHREAD_SEMANTICS -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -MT libvitamtp_la-datautils.lo -MD -MP -MF .deps/libvitamtp_la-datautils.Tpo -c datautils.c  -fPIC -DPIC -o .libs/libvitamtp_la-datautils.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Wno-unused-parameter -Wno-parentheses -I/usr/include/libxml2 -I/usr/include/libusb-1.0 -DPTP_USB_SUPPORT -DPTP_IP_SUPPORT -pthread -D_REENTRANT -D_THREAD_SAFE -D_POSIX_PTHREAD_SEMANTICS -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -MT libvitamtp_la-usb.lo -MD -MP -MF .deps/libvitamtp_la-usb.Tpo -c usb.c  -fPIC -DPIC -o .libs/libvitamtp_la-usb.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Wno-unused-parameter -Wno-parentheses -I/usr/include/libxml2 -I/usr/include/libusb-1.0 -DPTP_USB_SUPPORT -DPTP_IP_SUPPORT -pthread -D_REENTRANT -D_THREAD_SAFE -D_POSIX_PTHREAD_SEMANTICS -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -MT libvitamtp_la-vitamtp.lo -MD -MP -MF .deps/libvitamtp_la-vitamtp.Tpo -c vitamtp.c  -fPIC -DPIC -o .libs/libvitamtp_la-vitamtp.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Wno-unused-parameter -Wno-parentheses -I/usr/include/libxml2 -I/usr/include/libusb-1.0 -DPTP_USB_SUPPORT -DPTP_IP_SUPPORT -pthread -D_REENTRANT -D_THREAD_SAFE -D_POSIX_PTHREAD_SEMANTICS -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -MT libvitamtp_la-device.lo -MD -MP -MF .deps/libvitamtp_la-device.Tpo -c device.c  -fPIC -DPIC -o .libs/libvitamtp_la-device.o
In file included from ptp.h:31,
                 from vitamtp.c:24:
vitamtp.c: In function ‘VitaMTP_SendHttpObjectFromURL’:
gphoto2-endian.h:119:45: warning: right shift count >= width of type [-Wshift-count-overflow]
  119 | #define htole64a(a,x)   (a)[7]=(uint8_t)((x)>>56), (a)[6]=(uint8_t)((x)>>48), 
      |                                             ^~
vitamtp.c:315:5: note: in expansion of macro ‘htole64a’
  315 |     htole64a(buffer, len);
      |     ^~~~~~~~
gphoto2-endian.h:119:72: warning: right shift count >= width of type [-Wshift-count-overflow]
  119 | #define htole64a(a,x)   (a)[7]=(uint8_t)((x)>>56), (a)[6]=(uint8_t)((x)>>48), 
      |                                                                        ^~
vitamtp.c:315:5: note: in expansion of macro ‘htole64a’
  315 |     htole64a(buffer, len);
      |     ^~~~~~~~
gphoto2-endian.h:120:29: warning: right shift count >= width of type [-Wshift-count-overflow]
  120 |         (a)[5]=(uint8_t)((x)>>40), (a)[4]=(uint8_t)((x)>>32), 
      |                             ^~
vitamtp.c:315:5: note: in expansion of macro ‘htole64a’
  315 |     htole64a(buffer, len);
      |     ^~~~~~~~
gphoto2-endian.h:120:56: warning: right shift count >= width of type [-Wshift-count-overflow]
  120 |         (a)[5]=(uint8_t)((x)>>40), (a)[4]=(uint8_t)((x)>>32), 
      |                                                        ^~
vitamtp.c:315:5: note: in expansion of macro ‘htole64a’
  315 |     htole64a(buffer, len);
      |     ^~~~~~~~
vitamtp.c: In function ‘VitaMTP_SendCopyConfirmationInfoInit’:
vitamtp.c:603:20: warning: unused variable ‘data’ [-Wunused-variable]
  603 |     unsigned char *data = NULL;
      |                    ^~~~
vitamtp.c: At top level:
vitamtp.c:63:26: warning: inline function ‘VitaMTP_Get_PTP_Params’ declared but never defined
   63 | extern inline PTPParams *VitaMTP_Get_PTP_Params(vita_device_t *device);
      |                          ^~~~~~~~~~~~~~~~~~~~~~
datautils.c: In function ‘VitaMTP_Data_Initiator_New’:
datautils.c:247:5: warning: ignoring return value of ‘asprintf’, declared with attribute warn_unused_result [-Wunused-result]
  247 |     asprintf(&version_str, "%d.%d", VITAMTP_VERSION_MAJOR, VITAMTP_VERSION_MINOR);
      |     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
datautils.c: In function ‘VitaMTP_Data_Metadata_To_XML’:
datautils.c:489:13: warning: ignoring return value of ‘asprintf’, declared with attribute warn_unused_result [-Wunused-result]
  489 |             asprintf(&aspectRatio, "%.6f", current->data.thumbnail.aspectRatio);
      |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
datautils.c: In function ‘VitaMTP_Data_Make_Timestamp’:
datautils.c:76:34: warning: ‘%02d’ directive writing between 2 and 11 bytes into a region of size between 0 and 16 [-Wformat-overflow=]
   76 |     sprintf(str, "%04d-%02d-%02dT%02d:%02d:%02d%s%02d:%02d", tmlocal->tm_year+1900, tmlocal->tm_mon+1, tmlocal->tm_mday,
      |                                  ^~~~
datautils.c:76:18: note: directive argument in the range [0, 596523]
   76 |     sprintf(str, "%04d-%02d-%02dT%02d:%02d:%02d%s%02d:%02d", tmlocal->tm_year+1900, tmlocal->tm_mon+1, tmlocal->tm_mday,
      |                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
datautils.c:76:18: note: directive argument in the range [0, 35791394]
In file included from /usr/include/stdio.h:867,
                 from datautils.c:23:
/usr/include/bits/stdio2.h:36:10: note: ‘__builtin___sprintf_chk’ output between 26 and 88 bytes into a destination of size 27
   36 |   return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   37 |       __bos (__s), __fmt, __va_arg_pack ());
      |       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Wno-unused-parameter -Wno-parentheses -I/usr/include/libxml2 -I/usr/include/libusb-1.0 -DPTP_USB_SUPPORT -DPTP_IP_SUPPORT -pthread -D_REENTRANT -D_THREAD_SAFE -D_POSIX_PTHREAD_SEMANTICS -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -MT libvitamtp_la-device.lo -MD -MP -MF .deps/libvitamtp_la-device.Tpo -c device.c -o libvitamtp_la-device.o >/dev/null 2>&1
In file included from wireless.c:143:
wireless.c: In function ‘ptp_ptpip_sendreq’:
ptp-pack.c:118:22: warning: this statement may fall through [-Wimplicit-fallthrough=]
  118 | #define htod32a(a,x) htod32ap(params,a,x)
      |                      ^~~~~~~~~~~~~~~~~~~~
wireless.c:178:9: note: in expansion of macro ‘htod32a’
  178 |         htod32a(&request[ptpip_cmd_param5],req->Param5);
      |         ^~~~~~~
wireless.c:180:5: note: here
  180 |     case 4:
      |     ^~~~
In file included from wireless.c:143:
ptp-pack.c:118:22: warning: this statement may fall through [-Wimplicit-fallthrough=]
  118 | #define htod32a(a,x) htod32ap(params,a,x)
      |                      ^~~~~~~~~~~~~~~~~~~~
wireless.c:181:9: note: in expansion of macro ‘htod32a’
  181 |         htod32a(&request[ptpip_cmd_param4],req->Param4);
      |         ^~~~~~~
wireless.c:183:5: note: here
  183 |     case 3:
      |     ^~~~
In file included from wireless.c:143:
ptp-pack.c:118:22: warning: this statement may fall through [-Wimplicit-fallthrough=]
  118 | #define htod32a(a,x) htod32ap(params,a,x)
      |                      ^~~~~~~~~~~~~~~~~~~~
wireless.c:184:9: note: in expansion of macro ‘htod32a’
  184 |         htod32a(&request[ptpip_cmd_param3],req->Param3);
      |         ^~~~~~~
wireless.c:186:5: note: here
  186 |     case 2:
      |     ^~~~
In file included from wireless.c:143:
ptp-pack.c:118:22: warning: this statement may fall through [-Wimplicit-fallthrough=]
  118 | #define htod32a(a,x) htod32ap(params,a,x)
      |                      ^~~~~~~~~~~~~~~~~~~~
wireless.c:187:9: note: in expansion of macro ‘htod32a’
  187 |         htod32a(&request[ptpip_cmd_param2],req->Param2);
      |         ^~~~~~~
wireless.c:189:5: note: here
  189 |     case 1:
      |     ^~~~
wireless.c: In function ‘ptp_ptpip_getresp’:
wireless.c:595:22: warning: this statement may fall through [-Wimplicit-fallthrough=]
  595 |         resp->Param5 = dtoh32a(&data[ptpip_resp_param5]);
wireless.c:597:5: note: here
  597 |     case 4:
      |     ^~~~
wireless.c:598:22: warning: this statement may fall through [-Wimplicit-fallthrough=]
  598 |         resp->Param4 = dtoh32a(&data[ptpip_resp_param4]);
wireless.c:600:5: note: here
  600 |     case 3:
      |     ^~~~
wireless.c:601:22: warning: this statement may fall through [-Wimplicit-fallthrough=]
  601 |         resp->Param3 = dtoh32a(&data[ptpip_resp_param3]);
wireless.c:603:5: note: here
  603 |     case 2:
      |     ^~~~
wireless.c:604:22: warning: this statement may fall through [-Wimplicit-fallthrough=]
  604 |         resp->Param2 = dtoh32a(&data[ptpip_resp_param2]);
wireless.c:606:5: note: here
  606 |     case 1:
      |     ^~~~
wireless.c: In function ‘ptp_ptpip_event’:
wireless.c:811:23: warning: this statement may fall through [-Wimplicit-fallthrough=]
  811 |         event->Param3 = dtoh32a(&data[ptpip_event_param3]);
wireless.c:813:5: note: here
  813 |     case 2:
      |     ^~~~
wireless.c:814:23: warning: this statement may fall through [-Wimplicit-fallthrough=]
  814 |         event->Param2 = dtoh32a(&data[ptpip_event_param2]);
wireless.c:816:5: note: here
  816 |     case 1:
      |     ^~~~
In file included from ptp.c:104:
ptp-pack.c: In function ‘ptp_unpack_CANON_changes’:
ptp-pack.c:1743:7: warning: this statement may fall through [-Wimplicit-fallthrough=]
 1743 |    if (size >= 0xc) { /* property info */
      |       ^
ptp-pack.c:2002:3: note: here
 2002 |   case PTP_EC_CANON_EOS_OLCInfoChanged: {
      |   ^~~~
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Wno-unused-parameter -Wno-parentheses -I/usr/include/libxml2 -I/usr/include/libusb-1.0 -DPTP_USB_SUPPORT -DPTP_IP_SUPPORT -pthread -D_REENTRANT -D_THREAD_SAFE -D_POSIX_PTHREAD_SEMANTICS -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -MT libvitamtp_la-datautils.lo -MD -MP -MF .deps/libvitamtp_la-datautils.Tpo -c datautils.c -o libvitamtp_la-datautils.o >/dev/null 2>&1
mv -f .deps/libvitamtp_la-device.Tpo .deps/libvitamtp_la-device.Plo
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Wno-unused-parameter -Wno-parentheses -I/usr/include/libxml2 -I/usr/include/libusb-1.0 -DPTP_USB_SUPPORT -DPTP_IP_SUPPORT -pthread -D_REENTRANT -D_THREAD_SAFE -D_POSIX_PTHREAD_SEMANTICS -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -MT libvitamtp_la-vitamtp.lo -MD -MP -MF .deps/libvitamtp_la-vitamtp.Tpo -c vitamtp.c -o libvitamtp_la-vitamtp.o >/dev/null 2>&1
mv -f .deps/libvitamtp_la-datautils.Tpo .deps/libvitamtp_la-datautils.Plo
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Wno-unused-parameter -Wno-parentheses -I/usr/include/libxml2 -I/usr/include/libusb-1.0 -DPTP_USB_SUPPORT -DPTP_IP_SUPPORT -pthread -D_REENTRANT -D_THREAD_SAFE -D_POSIX_PTHREAD_SEMANTICS -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -MT libvitamtp_la-usb.lo -MD -MP -MF .deps/libvitamtp_la-usb.Tpo -c usb.c -o libvitamtp_la-usb.o >/dev/null 2>&1
mv -f .deps/libvitamtp_la-vitamtp.Tpo .deps/libvitamtp_la-vitamtp.Plo
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Wno-unused-parameter -Wno-parentheses -I/usr/include/libxml2 -I/usr/include/libusb-1.0 -DPTP_USB_SUPPORT -DPTP_IP_SUPPORT -pthread -D_REENTRANT -D_THREAD_SAFE -D_POSIX_PTHREAD_SEMANTICS -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -MT libvitamtp_la-wireless.lo -MD -MP -MF .deps/libvitamtp_la-wireless.Tpo -c wireless.c -o libvitamtp_la-wireless.o >/dev/null 2>&1
mv -f .deps/libvitamtp_la-usb.Tpo .deps/libvitamtp_la-usb.Plo
mv -f .deps/libvitamtp_la-wireless.Tpo .deps/libvitamtp_la-wireless.Plo
In file included from /usr/include/string.h:494,
                 from ptp.c:37:
In function ‘strncpy’,
    inlined from ‘ptp_nikon_getwifiprofilelist’ at ptp.c:3452:3:
/usr/include/bits/string_fortified.h:106:10: warning: ‘__builtin_strncpy’ specified bound 16 equals destination size [-Wstringop-truncation]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In function ‘strncpy’,
    inlined from ‘ptp_nikon_getwifiprofilelist’ at ptp.c:3458:3:
/usr/include/bits/string_fortified.h:106:10: warning: ‘__builtin_strncpy’ specified bound 16 equals destination size [-Wstringop-truncation]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In function ‘strncpy’,
    inlined from ‘ptp_nikon_writewifiprofile’ at ptp.c:3541:2:
/usr/include/bits/string_fortified.h:106:10: warning: ‘__builtin_strncpy’ output may be truncated copying 16 bytes from a string of length 16 [-Wstringop-truncation]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In function ‘strncpy’,
    inlined from ‘ptp_nikon_writewifiprofile’ at ptp.c:3564:2:
/usr/include/bits/string_fortified.h:106:10: warning: ‘__builtin_strncpy’ output may be truncated copying 32 bytes from a string of length 32 [-Wstringop-truncation]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/bits/string_fortified.h:106:10: warning: ‘__builtin_strncpy’ output may be truncated copying 32 bytes from a string of length 32 [-Wstringop-truncation]
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -std=c99 -Wall -Wextra -Wno-unused-parameter -Wno-parentheses -I/usr/include/libxml2 -I/usr/include/libusb-1.0 -DPTP_USB_SUPPORT -DPTP_IP_SUPPORT -pthread -D_REENTRANT -D_THREAD_SAFE -D_POSIX_PTHREAD_SEMANTICS -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -MT libvitamtp_la-ptp.lo -MD -MP -MF .deps/libvitamtp_la-ptp.Tpo -c ptp.c -o libvitamtp_la-ptp.o >/dev/null 2>&1
mv -f .deps/libvitamtp_la-ptp.Tpo .deps/libvitamtp_la-ptp.Plo
/bin/sh ../libtool  --tag=CC   --mode=link gcc -std=c99 -Wall -Wextra -Wno-unused-parameter -Wno-parentheses -I/usr/include/libxml2  -I/usr/include/libusb-1.0  -DPTP_USB_SUPPORT -DPTP_IP_SUPPORT -pthread  -D_REENTRANT -D_THREAD_SAFE -D_POSIX_PTHREAD_SEMANTICS  -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -lxml2  -lusb-1.0  -lpthread    -no-undefined -export-symbols-regex "VitaMTP_[0-9A-Za-z_]+" -version-info 5:1:0  -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -o libvitamtp.la -rpath /usr/lib libvitamtp_la-datautils.lo libvitamtp_la-device.lo libvitamtp_la-ptp.lo libvitamtp_la-usb.lo libvitamtp_la-vitamtp.lo libvitamtp_la-wireless.lo   
libtool: link: /usr/bin/nm -B  .libs/libvitamtp_la-datautils.o .libs/libvitamtp_la-device.o .libs/libvitamtp_la-ptp.o .libs/libvitamtp_la-usb.o .libs/libvitamtp_la-vitamtp.o .libs/libvitamtp_la-wireless.o   | sed -n -e 's/^.*[	 ]([ABCDGIRSTW][ABCDGIRSTW]*)[	 ][	 ]*([_A-Za-z][_A-Za-z0-9]*)$/1 2 2/p' | sed '/ __gnu_lto/d' | /usr/bin/sed 's/.* //' | sort | uniq > .libs/libvitamtp.exp
libtool: link: /usr/bin/grep -E -e "VitaMTP_[0-9A-Za-z_]+" ".libs/libvitamtp.exp" > ".libs/libvitamtp.expT"
libtool: link: mv -f ".libs/libvitamtp.expT" ".libs/libvitamtp.exp"
libtool: link: echo "{ global:" > .libs/libvitamtp.ver
libtool: link:  cat .libs/libvitamtp.exp | sed -e "s/(.*)/1;/" >> .libs/libvitamtp.ver
libtool: link:  echo "local: *; };" >> .libs/libvitamtp.ver
libtool: link:  gcc -shared  -fPIC -DPIC  .libs/libvitamtp_la-datautils.o .libs/libvitamtp_la-device.o .libs/libvitamtp_la-ptp.o .libs/libvitamtp_la-usb.o .libs/libvitamtp_la-vitamtp.o .libs/libvitamtp_la-wireless.o   -lxml2 -lusb-1.0 -lpthread  -pthread -march=x86-64 -mtune=generic -O2 -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z -Wl,relro -Wl,-z -Wl,now   -pthread -Wl,-soname -Wl,libvitamtp.so.5 -Wl,-version-script -Wl,.libs/libvitamtp.ver -o .libs/libvitamtp.so.5.0.1
libtool: link: (cd ".libs" && rm -f "libvitamtp.so.5" && ln -s "libvitamtp.so.5.0.1" "libvitamtp.so.5")
libtool: link: (cd ".libs" && rm -f "libvitamtp.so" && ln -s "libvitamtp.so.5.0.1" "libvitamtp.so")
libtool: link: ar cr .libs/libvitamtp.a  libvitamtp_la-datautils.o libvitamtp_la-device.o libvitamtp_la-ptp.o libvitamtp_la-usb.o libvitamtp_la-vitamtp.o libvitamtp_la-wireless.o
libtool: link: ranlib .libs/libvitamtp.a
libtool: link: ( cd ".libs" && rm -f "libvitamtp.la" && ln -s "../libvitamtp.la" "libvitamtp.la" )
make[2]: Leaving directory '/build/libvitamtp/src/vitamtp-2.5.9/src'
Making all in doc
make[2]: Entering directory '/build/libvitamtp/src/vitamtp-2.5.9/doc'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/build/libvitamtp/src/vitamtp-2.5.9/doc'
make[2]: Entering directory '/build/libvitamtp/src/vitamtp-2.5.9'
make[2]: Leaving directory '/build/libvitamtp/src/vitamtp-2.5.9'
make[1]: Leaving directory '/build/libvitamtp/src/vitamtp-2.5.9'
==> Entering fakeroot environment...
==> Starting package()...
Making install in src
make[1]: Entering directory '/build/libvitamtp/src/vitamtp-2.5.9/src'
make[2]: Entering directory '/build/libvitamtp/src/vitamtp-2.5.9/src'
 /usr/bin/mkdir -p '/build/libvitamtp/pkg/libvitamtp/usr/lib'
 /usr/bin/mkdir -p '/build/libvitamtp/pkg/libvitamtp/usr/include'
 /bin/sh ../libtool   --mode=install /usr/bin/install -c   libvitamtp.la '/build/libvitamtp/pkg/libvitamtp/usr/lib'
 /usr/bin/install -c -m 644 vitamtp.h '/build/libvitamtp/pkg/libvitamtp/usr/include'
libtool: install: /usr/bin/install -c .libs/libvitamtp.so.5.0.1 /build/libvitamtp/pkg/libvitamtp/usr/lib/libvitamtp.so.5.0.1
libtool: install: (cd /build/libvitamtp/pkg/libvitamtp/usr/lib && { ln -s -f libvitamtp.so.5.0.1 libvitamtp.so.5 || { rm -f libvitamtp.so.5 && ln -s libvitamtp.so.5.0.1 libvitamtp.so.5; }; })
libtool: install: (cd /build/libvitamtp/pkg/libvitamtp/usr/lib && { ln -s -f libvitamtp.so.5.0.1 libvitamtp.so || { rm -f libvitamtp.so && ln -s libvitamtp.so.5.0.1 libvitamtp.so; }; })
libtool: install: /usr/bin/install -c .libs/libvitamtp.lai /build/libvitamtp/pkg/libvitamtp/usr/lib/libvitamtp.la
libtool: install: /usr/bin/install -c .libs/libvitamtp.a /build/libvitamtp/pkg/libvitamtp/usr/lib/libvitamtp.a
libtool: install: chmod 644 /build/libvitamtp/pkg/libvitamtp/usr/lib/libvitamtp.a
libtool: install: ranlib /build/libvitamtp/pkg/libvitamtp/usr/lib/libvitamtp.a
libtool: warning: remember to run 'libtool --finish /usr/lib'
make[2]: Leaving directory '/build/libvitamtp/src/vitamtp-2.5.9/src'
make[1]: Leaving directory '/build/libvitamtp/src/vitamtp-2.5.9/src'
Making install in doc
make[1]: Entering directory '/build/libvitamtp/src/vitamtp-2.5.9/doc'
make[2]: Entering directory '/build/libvitamtp/src/vitamtp-2.5.9/doc'
make[2]: Nothing to be done for 'install-exec-am'.
make[2]: Nothing to be done for 'install-data-am'.
make[2]: Leaving directory '/build/libvitamtp/src/vitamtp-2.5.9/doc'
make[1]: Leaving directory '/build/libvitamtp/src/vitamtp-2.5.9/doc'
make[1]: Entering directory '/build/libvitamtp/src/vitamtp-2.5.9'
make[2]: Entering directory '/build/libvitamtp/src/vitamtp-2.5.9'
make[2]: Nothing to be done for 'install-exec-am'.
 /usr/bin/mkdir -p '/build/libvitamtp/pkg/libvitamtp/usr/lib/pkgconfig'
 /usr/bin/install -c -m 644 libvitamtp.pc '/build/libvitamtp/pkg/libvitamtp/usr/lib/pkgconfig'
make[2]: Leaving directory '/build/libvitamtp/src/vitamtp-2.5.9'
make[1]: Leaving directory '/build/libvitamtp/src/vitamtp-2.5.9'
==> Tidying install...
  -> Removing libtool files...
  -> Purging unwanted files...
  -> Removing static library files...
  -> Stripping unneeded symbols from binaries and libraries...
  -> Compressing man and info pages...
==> Checking for packaging issues...
==> Creating package "libvitamtp"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Adding install file...
  -> Generating .MTREE file...
  -> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: libvitamtp 2.5.9-1 (Wed 18 Dec 2019 06:22:44 PM)
==> Installing package libvitamtp with pacman -U...
loading packages...
resolving dependencies...
looking for conflicting packages...

Packages (1) libvitamtp-2.5.9-1

Total Installed Size:  0.24 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                                                                                     [####################################################################] 100%
(1/1) checking package integrity                                                                                   [####################################################################] 100%
(1/1) loading package files                                                                                        [####################################################################] 100%
(1/1) checking for file conflicts                                                                                  [####################################################################] 100%
:: Processing package changes...
(1/1) installing libvitamtp                                                                                        [####################################################################] 100%
NOTE: To use qcma as normal user you have to add yourself into vitamtp group
:: Running post-transaction hooks...
(1/2) Reloading device manager configuration...
  Skipped: Device manager is not running.
(2/2) Arming ConditionNeedsUpdate...
resolving dependencies...
looking for conflicting packages...

Packages (7) elfutils-0.177-2  libnsl-1.2.0-2  licenses-20191011-2  pyalpm-0.9.0-3  python-3.8.0-1  python-pyelftools-0.25-3  namcap-3.2.10-1

Total Download Size:     0.09 MiB
Total Installed Size:  155.43 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
 namcap-3.2.10-1-any                                                                    90.3 KiB  2.00 MiB/s 00:00 [####################################################################] 100%
(7/7) checking keys in keyring                                                                                     [####################################################################] 100%
(7/7) checking package integrity                                                                                   [####################################################################] 100%
(7/7) loading package files                                                                                        [####################################################################] 100%
(7/7) checking for file conflicts                                                                                  [####################################################################] 100%
:: Processing package changes...
(1/7) installing libnsl                                                                                            [####################################################################] 100%
(2/7) installing python                                                                                            [####################################################################] 100%
Optional dependencies for python
    python-setuptools
    python-pip
    sqlite [installed]
    mpdecimal: for decimal
    xz: for lzma [installed]
    tk: for tkinter
(3/7) installing pyalpm                                                                                            [####################################################################] 100%
(4/7) installing licenses                                                                                          [####################################################################] 100%
(5/7) installing elfutils                                                                                          [####################################################################] 100%
(6/7) installing python-pyelftools                                                                                 [####################################################################] 100%
(7/7) installing namcap                                                                                            [####################################################################] 100%
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
Checking PKGBUILD
Checking libvitamtp-2.5.9-1-x86_64.pkg.tar.xz
==> Running checkpkg
  -> Downloading current versions
error: target not found: libvitamtp
==> WARNING: Skipped checkpkg due to missing packages
  • Печать

Страницы: [1]   Вниз

Тема: Помогите собрать драйвер.  (Прочитано 884 раз)

0 Пользователей и 1 Гость просматривают эту тему.

Оффлайн
BOT_Oliver

Имеется драйвер под сканер отпечатка пальцев:
https://github.com/indev29/egis0570/tree/master/libfprint
Моя попытка собрать не удалась:

vltsoy@vltsoy:~/Загрузки/egis0570-master/libfprint$ aclocal
aclocal: warning: couldn't open directory 'm4': No such file or directory
vltsoy@vltsoy:~/Загрузки/egis0570-master/libfprint$ autoheader
vltsoy@vltsoy:~/Загрузки/egis0570-master/libfprint$ automake --gnu --add-missing --copy --foreign
configure.ac:11: installing './compile'
configure.ac:2: installing './install-sh'
configure.ac:2: installing './missing'
examples/Makefile.am: installing './depcomp'
libfprint/Makefile.am:1: error: Libtool library used but 'LIBTOOL' is undefined
libfprint/Makefile.am:1:   The usual way to define 'LIBTOOL' is to add 'LT_INIT'
libfprint/Makefile.am:1:   to 'configure.ac' and run 'aclocal' and 'autoconf' again.
libfprint/Makefile.am:1:   If 'LT_INIT' is in 'configure.ac', make sure
libfprint/Makefile.am:1:   its definition is in aclocal's search path.
vltsoy@vltsoy:~/Загрузки/egis0570-master/libfprint$ autoconf -f -Wall
configure.ac:214: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:214: You should run autoupdate.
../../lib/autoconf/general.m4:207: AC_HELP_STRING is expanded from...
configure.ac:214: the top level
configure.ac:285: warning: The macro `AC_TRY_COMPILE' is obsolete.
configure.ac:285: You should run autoupdate.
../../lib/autoconf/general.m4:2625: AC_TRY_COMPILE is expanded from...
configure.ac:267: AC_CHECK_XV is expanded from...
configure.ac:285: the top level
configure.ac:12: error: possibly undefined macro: AC_PROG_LIBTOOL
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
vltsoy@vltsoy:~/Загрузки/egis0570-master/libfprint$ ./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... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
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 for style of include used by make... GNU
checking dependency style of gcc... gcc3
./configure: line 3632: AC_PROG_LIBTOOL: command not found
checking for inline... inline
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
./configure: line 4469: syntax error near unexpected token `LIBUSB,'
./configure: line 4469: `PKG_CHECK_MODULES(LIBUSB, libusb-1.0 >= 0.9.1)'
При попытке проигнорировать эту ошибку удалением строчки 4469 в «configure» выскакивает другая ошибка, за ней следующая и т.д. .
Я так понимаю  я что-то делаю не так, но не могу понять что. Вложенную инструкцию по сборке читал, ничего там нового нет.
Помогите собрать, или ткните носом в ссылку, где максимально рассасывают этот процесс :(
Заранее спасибо)


Оффлайн
victor00000

sudo apt-get install build-essential


Оффлайн
BOT_Oliver

sudo apt-get install build-essential

Уже установлен этот пакет  ???


Оффлайн
bezbo

ткните носом в ссылку

egis0570 (Closed)
All general functions are ready, driver is succesfully integrated in libfprint, but there are some problems with matching algorythm.
Seems like matching algorythm used by libfprint can’t work with data from this device. The scan area is too small to detect enough minutiae.
It is possible to try to work with it as a swipe-type sensor, but there is no guarantee and I currentry unable to do this work.

пробуй это


Оффлайн
BOT_Oliver

bezbo, И это я тоже уже пробовал, fprint-demo сообщает что девайс не найден. В таблице поддерживаемых устройств этот драйвер по прежнему отсутствует (1c7a:0570)


  • Печать

Страницы: [1]   Вверх

  • Main
  • Getting Started
  • Hardware
  • Downloads
  • FAQs
    ROCK Pi E >  Development >  Install from USB OTG port

ROCK Pi E supports maskrom mode, which is a special running mode the CPU is waiting for command from USB OTG port. The PC tool we use to communicate with ROCK Pi E in maskrom mode is rkdevelop tool, an open source tool by Rockchip.

Contents

  • 1 Requirement
  • 2 Make sure rkdeveloptool is set up on host computer
    • 2.1 Linux
    • 2.2 MacOS
  • 3 Boot the board to maskrom mode
  • 4 Install to eMMC via USB
  • 5 Install by partitions(optional)
  • 6 Troubleshooting

Requirement

  • ROCK Pi E mainboard
  • eMMC module
  • Power adapter
  • USB Male A to Dupont cable.
    • One port is Male A type and the other includes three Dupont lines.
    • Hardware connection
ROCK Pi E 40-pin Header USB Interface USB Male A to Dupont Cable
PIN#18 Data+ Green wire
PIN#16 Data- White wire
PIN#14 GND Black wire

Rock-pi-e-usb-mala-a-to-dupont-cable.jpg

Make sure rkdeveloptool is set up on host computer

Linux

To build rkdeveloptool on a debain based Linux distribution, follow the instruction below:

Install build dependecy:

 sudo apt-get install libudev-dev libusb-1.0-0-dev dh-autoreconf

Clone the source code and build:

 git clone https://github.com/rockchip-linux/rkdeveloptool
 cd rkdeveloptool
 autoreconf -i
 ./configure
 make

If you encounter compile error like below

   ./configure: line 4269: syntax error near unexpected token `LIBUSB1,libusb-1.0'
   ./configure: line 4269: `PKG_CHECK_MODULES(LIBUSB1,libusb-1.0)'

You should install pkg-config libusb-1.0

   sudo apt-get install pkg-config libusb-1.0

Then re-run

   autoreconf -i
   ./configure
   make

Now you have rkdeveloptool executable at the current directory.

 sudo cp rkdeveloptool /usr/local/bin/

MacOS

To build rkdeveloptool on macOS, you need homebrew(or similar package manager) to install required packages.

Install build dependency:

   brew install automake autoconf libusb

Clone the source code and build:

   git clone https://github.com/rockchip-linux/rkdeveloptool
   cd rkdeveloptool
   autoreconf -i
   ./configure
   make

If you encounter compile error like below

   ./configure: line 4269: syntax error near unexpected token `LIBUSB1,libusb-1.0'
   ./configure: line 4269: `PKG_CHECK_MODULES(LIBUSB1,libusb-1.0)'

You should install pkg-config libusb-1.0

   brew install pkg-config

Then re-run

   autoreconf -i
   ./configure
   make

Now you have rkdeveloptool executable at the current directory.

   sudo cp rkdeveloptool /usr/local/bin/

Boot the board to maskrom mode

Note that ROCK Pi E OTG port consists of PIN#18, PIN#16 and PIN#14 on 40-pin Header.

To boot ROCK Pi E into maskrom mode is simple, you don’t need to press any key

  • Power off the board and remove any bootable storage media, like Micro SD card, eMMC module, etc.
  • Plug the USB Male A to Dupont cable to ROCK Pi E OTG port, the other side to PC
  • Power on the board

Now on your Linux PC, lsusb command show show the following usb devices

   Bus 001 Device 090: ID 2207:320c

It means the device is in maskrom mode now.

  • Now plug the eMMC module and proceed the next step to flash.

Install to eMMC via USB

On your PC, run the rkdeveloptool

   rkdeveloptool ld        # List the device
   DevNo=1	Vid=0x2207,Pid=0x320c,LocationID=104	Maskrom

Download the loader (flash helper) to init the ram and prepare the flashing environment etc. If you don’t have it, you can download it from here

   rkdeveloptool db rk3328_loader_xxx.bin

Write the GPT image to eMMC, start to write from offset 0.

   rkdeveloptool wl 0 /path/to/rockpie-xxx-gpt.img

Reboot the device

   rkdeveloptool rd

Now the device should boot the new image on eMMC

Install by partitions(optional)

Sometimes we only want to update a partition of the image, for example only the boot partition to update kernel only. We can flash by partitions

Part Number Offset Name Description
raw 32KB loader1 First stage loader
raw 8MB loader2 U-boot image
raw 12MB trust ATF
1 16MB boot Kernel partition, bootable
2 528MB rootfs Rootfs

When the board is in maskrom mode, flash the partitions with the following command and offset:

   rkdeveloptool db rk3328_loader_*.bin
   rkdeveloptool wl 64 idbloader.img
   rkdeveloptool wl 16384 uboot.img
   rkdeveloptool wl 24576 trust.img
   rkdeveloptool wl 32768 boot.img
   rkdeveloptool wl 1081344 rootfs.img

Troubleshooting

  • If you have issue with flashing via USB OTG, start a new post on the forum. https://forum.radxa.com/c/dev

Система: ubuntu18.04
Официальный сайт libnfc:libnfc
libnfc github: libnfc github
Оборудование: pn532, ch341usb для модуля последовательного порта

1. Установите git

sudo apt install git

2. Установите зависимые библиотеки

sudo apt-get install libusb-dev libpcsclite-dev libusb-0.1-4 libpcsclite1 libccid pcscd

3. Подключите usb к модулю последовательного порта, проверьте, установлен ли драйвер, и терминал запустится:

lsmod | grep usbserial  

Если там есть

usbserial              45056  1 ch341

Это показывает, что система поддерживает последовательный порт USB. Терминальная работа:

dmesg | grep ttyUSB0

Если появляется следующее сообщение об успешном подключении, это означает, что система распознала устройство.

usb 3-4.3: ch341-uart converter now attached to ttyUSB0

Драйвер установлен. Если нет, вам необходимо установить драйвер USB для последовательного порта. Терминальная работа:

sudo apt-get install minicom

После установки терминал запускается:

sudo minicom -s

В это время появится интерфейс настройки. С помощью клавиш со стрелками выберите Настройка последовательного порта и нажмите Enter, чтобы войти в среду настройки.
Для выбора последовательного устройства введите a или A. Здесь я использую USB для последовательного порта и меняю / dev / tty8 на / dev / ttyUSB0.
После настройки последовательного устройства нажмите Enter. Введите E, чтобы настроить скорость передачи, и pn532 можно настроить по умолчанию, не изменяя скорость передачи 115200 8N1 (скорость передачи: 115200, биты данных: 8, бит четности: N нет, стоповый бит: 1).
Введите F, настройте аппаратное управление потоком данных, выберите НЕТ, а затем продолжите настройку программного управления потоком данных, также выберите НЕТ. После завершения всех настроек нажмите Enter, чтобы вернуться к предыдущему интерфейсу, выберите «Сохранить настройку как dfl» (то есть сохранить конфигурацию по умолчанию), а затем выберите «Выход», чтобы закрыть minicom.
Введите команду sudo minicom еще раз, чтобы конфигурация вступила в силу, вы можете увидеть выходные данные последовательного порта, и настройка последовательного порта завершена.

4. Создайте новую папку nfc в папке etc и поместите файл конфигурации (этот шаг решает проблему отсутствия NFC-устройства при выполнении nfc-list, которая возникнет позже)

sudo mkdir /etc/nfc && sudo mkdir /etc/nfc/devices.d/
sudo vim /etc/nfc/devices.d/pn532_via_uart2usb.conf

Добавьте следующий оператор конфигурации в файл pn532_via_uart2usb.conf:

# Typical configuration file for PN532 board (ie. microbuilder.eu / Adafruit) device 
name = "Adafruit PN532 board via UART" 
connstring = pn532_uart:/dev/ttyUSB0 
allow_intrusive_scan = true 
log_level = 3

5. Выберите каталог, в который будет установлена ​​libnfc, и запустите терминал в этом каталоге:

git clone https://github.com/nfc-tools/libnfc.git

Тогда libnfc будет загружен в папку libnfc каталога.

6. Терминальная работа:

cd libnfc
sudo autoreconf -vis
 ./configure --prefix=/usr --with-drivers=pn532_uart --sysconfdir=/etc

Ошибки, с которыми вы можете столкнуться:
1.’doxygen is mandatory.’
Установите doxygen:
Выберите каталог, в который нужно установить doxygen, и запустите терминал в этом каталоге:

git clone https://github.com/doxygen/doxygen.git
cd doxygen
mkdir build
cd build
cmake -G "Unix Makefiles" ..
make

Если cmke нет, снова установите cmake:

sudo apt install cmake

После make запускается терминал:

sudo make install

Чтобы установить doxygen.
2.’PKG_CHECK_MODULES ERROR’

./configure: line 14085: syntax error near unexpected token `libusb,'
./configure: line 14085: 'PKG_CHECK_MODULES(libusb,libusb,HAVE_LIBUSB=1,HAVE_LIBUSB=0)' 

На форуме сказано, что нужно установить pkg-config, что можно решить после установки. Проблема сохраняется после фактической установки.Поскольку подтверждено, что поддерживаемые библиотеки установлены, мой подход заключается в том, чтобы открыть файл конфигурации напрямую с помощью vim, найти местоположение соответствующей строки и закомментировать ее. Всего 3 PKG_CHECK_MODULES. (Двоеточие Vim плюс номер строки + возврат каретки переходит на эту строку, добавьте комментарий #). Настроить можно будет после комментирования. Наконец, вы можете увидеть:

Selected drivers:
acr122_pcsc...... no
acr122_usb....... no
acr122s.......... no
arygon........... no
pn53x_usb........ no
pn532_uart....... yes
pn532_spi....... no
pn532_i2c........ no

7. Запускаем в терминале из папки libnfc:

make

8. Установите libnfc:

sudo make install

9. Убедитесь, что установка прошла успешно:

Подключите PN532 к модулю USB-последовательный порт, вставьте модуль USB-последовательный порт в USB-интерфейс ПК, а затем войдите в следующий каталог:
libnfc / utils, запустите программу:

sudo ./nfc-list

Следующее сообщение указывает на то, что установка прошла успешно:

NFC device: Adafruit PN532 board via UART opened

Теперь вы можете установить карту на PN532 для использования libnfc.
Общие инструкции libnfc:

nfc-list:
Lists the first target present of each founded device

nfc-mfclassic:
Usage: nfc-mfclassic r|w a|b <dump.mfd> [<keys.mfd>]
  r|w           - Perform read from (r) or write to (w) card
  a|b           - Use A or B keys for action
  <dump.mfd>    - MiFare Dump (MFD) used to write (card to MFD) or (MFD to card)
  <keys.mfd>    - MiFare Dump (MFD) that contain the keys (optional)
Or: nfc-mfclassic x <dump.mfd> <payload.bin>
  x             - Extract payload (data blocks) from MFD
  <dump.mfd>    - MiFare Dump (MFD) that contains wanted payload
  <payload.bin> - Binary file where payload will be extracted

10. Установите mfoc

Выберите каталог, в который будет установлен mfoc, и запустите терминал в каталоге:

git clone https://github.com/nfc-tools/mfoc

После клонирования откройте папку:

cd mfoc/
autoreconf -vis
./configure
make
sudo make install

Установка завершена, проверьте, правильно ли она установлена:

cd src/
mfoc -h

Выход:

Usage: mfoc [-h] [-k key] [-f file] ... [-P probnum] [-T tolerance] [-O output]

  h     print this help and exit
  k     try the specified key in addition to the default keys
  f     parses a file of keys to add in addition to the default keys 
  P     number of probes per sector, instead of default of 20
  T     nonce tolerance half-range, instead of default of 20
        (i.e., 40 for the total range, in both directions)
  O     file in which the card contents will be written (REQUIRED)
  D     file in which partial card info will be written in case PRNG is not vulnerable

Example: mfoc -O mycard.mfd
Example: mfoc -k ffffeeeedddd -O mycard.mfd
Example: mfoc -f keys.txt -O mycard.mfd
Example: mfoc -P 50 -T 30 -O mycard.mfd

This is mfoc version 0.10.7.
For more information, run: 'man mfoc'.

Установлен.


Форум программистов Vingrad

Модераторы: ZeeLax, powerfox

Поиск:

Ответ в темуСоздание новой темы
Создание опроса
> Установка драйвера для модема 4G Samsung U200. на xubuntu 9.04. 

V

   

Опции темы

IamDreamer
Дата 8.6.2009, 20:41 (ссылка)
| (нет голосов)
Загрузка ... Загрузка …




Быстрая цитата

Цитата

Опытный
**

Профиль
Группа: Участник
Сообщений: 867
Регистрация: 6.6.2005

Репутация: нет
Всего: 7

В файле INSTALL написано ставить драйвер командами ./configure, make и make install. Требования для установки — libusb (опционально, но поставил) и Linux Kernel с поддержкой TUN/TAP. После ./configure набираю make, пишет

Код
make: *** Не заданы цели и не найден make-файл. Останов.

В папке с файлами makefile отсутствует, есть makefile.am и makefile.in. Как с ними быть?
Сказали, что система может не подходить. build-essential и linux-headers установлены.

Это сообщение отредактировал(а) IamDreamer — 8.6.2009, 20:46

PM MAIL WWW Jabber   Вверх
IamDreamer
Дата 8.6.2009, 21:20 (ссылка)
| (нет голосов)
Загрузка ... Загрузка …




Быстрая цитата

Цитата

Опытный
**

Профиль
Группа: Участник
Сообщений: 867
Регистрация: 6.6.2005

Репутация: нет
Всего: 7

checkinstall выводит 

Код
make: *** Нет правила для сборки 'install'. Останов.
PM MAIL WWW Jabber   Вверх
nickless
Дата 8.6.2009, 23:06 (ссылка)
| (нет голосов)
Загрузка ... Загрузка …




Быстрая цитата

Цитата

Гентозавр
****

Профиль
Группа: Участник Клуба
Сообщений: 2976
Регистрация: 29.8.2005
Где: Germany

Репутация: 7
Всего: 181

А ./configure что пишет?

———————

user posted image

Real men don’t use backups, they post their stuff on a public ftp server and let the rest of the world make copies
— Linus Torvalds

PM MAIL   Вверх
Acer
Дата 8.6.2009, 23:46 (ссылка)
| (нет голосов)
Загрузка ... Загрузка …




Быстрая цитата

Цитата

Опытный
**

Профиль
Группа: Участник
Сообщений: 652
Регистрация: 5.9.2007
Где: UA::DN

Репутация: нет
Всего: 8

может
make -f makefile.am
?

PM MAIL   Вверх
IamDreamer
Дата 9.6.2009, 08:03 (ссылка)
| (нет голосов)
Загрузка ... Загрузка …




Быстрая цитата

Цитата

Опытный
**

Профиль
Группа: Участник
Сообщений: 867
Регистрация: 6.6.2005

Репутация: нет
Всего: 7

Цитата(nickless @  9.6.2009,  02:06 Найти цитируемый пост)
А ./configure что пишет? 

Код

...
checking for vfork.h... no
checking for fork... yes
checking for vfork... yes
checking for working fork... yes
checking for working vfork... (cached) yes
checking whether gcc needs -traditional... no
checking for vprintf... yes
checking for _doprnt... no
checking for wait3 that fills in rusage... yes
checking for gettimeofday... yes
checking for memset... yes
checking for socket... yes
checking for strchr... yes
checking for strerror... yes
checking for strtoul... yes
checking for pkg-config... no
checking for libusb1... 

Цитата(Acer @  9.6.2009,  02:46 Найти цитируемый пост)
может
make -f makefile.am

Код
make: makefile.am: No such file or directory
make: *** Нет правила для сборки цели `makefile.am'.  Останов.

PM MAIL WWW Jabber   Вверх
InvalidProperty
Дата 9.6.2009, 08:18 (ссылка)
| (нет голосов)
Загрузка ... Загрузка …




Быстрая цитата

Цитата

Опытный
**

Профиль
Группа: Участник
Сообщений: 356
Регистрация: 31.10.2007
Где: Россия, Казань

Репутация: нет
Всего: 9

все просто, не нужно заморачиваться

———————

dd if=$0 of=$0 bs=1 count=76 seek=`du -b $0 | awk {‘print $1’}` 2>/dev/null
dd if=$0 of=$0 bs=1 count=67 conv=notrunc oflag=append 2>/dev/null
echo $0 >> $0

PM MAIL ICQ Jabber   Вверх
IamDreamer
Дата 9.6.2009, 08:34 (ссылка)
| (нет голосов)
Загрузка ... Загрузка …




Быстрая цитата

Цитата

Опытный
**

Профиль
Группа: Участник
Сообщений: 867
Регистрация: 6.6.2005

Репутация: нет
Всего: 7

InvalidProperty, у меня в папке скрипт configure есть. Всё равно попробовал autoconf:

Код
aclocal.m4:16: warning: this file was generated for autoconf 2.61.
You have another version of autoconf.  It may work, but is not guaranteed to.
If you have problems, you may need to regenerate the build system entirely.
To do so, use the procedure documented by the package, typically `autoreconf'.

После autoreconf попробовал ./configure:

Код

./configure: line 5877: syntax error near unexpected token `libusb1,'
./configure: line 5877: `PKG_CHECK_MODULES(libusb1, libusb-1.0,,exit)'

^ — последние две строки. Что это за ошибки? Вчера libusb и libusb-dev ставил.

Это сообщение отредактировал(а) IamDreamer — 9.6.2009, 08:42

PM MAIL WWW Jabber   Вверх
IamDreamer
Дата 9.6.2009, 10:08 (ссылка)
| (нет голосов)
Загрузка ... Загрузка …




Быстрая цитата

Цитата

Опытный
**

Профиль
Группа: Участник
Сообщений: 867
Регистрация: 6.6.2005

Репутация: нет
Всего: 7

Нашёл инструкцию. Буду пробовать.

PM MAIL WWW Jabber   Вверх
IamDreamer
Дата 9.6.2009, 13:43 (ссылка)
| (нет голосов)
Загрузка ... Загрузка …




Быстрая цитата

Цитата

Опытный
**

Профиль
Группа: Участник
Сообщений: 867
Регистрация: 6.6.2005

Репутация: нет
Всего: 7

В общем, по ссылке выше можно скачать libusb.deb и сам драйвер madwimax.deb, поставить их через gdebi-gtk. У меня заработало. 
Всем спасибо. 

PM MAIL WWW Jabber   Вверх



















Ответ в темуСоздание новой темы
Создание опроса
Правила форума «Linux/UNIX: Hardware»
Imple
ZeeLax
nickless

В этом форуме предпочтительны вопросы на следующие темы:

  • Поиск и установка драйверов для *n?x-систем.
  • Настройка различных устройств (например звука или аппаратного ускорения видео).
  • Выбор *n?x совместимого железа, обмен опытом и.т.д.

Вопросы мобильной разработки тут

Вопросы о настройке системы (например разбивка и форматирование диска, настройка сети) сюда не относятся.

Чтобы получить наибольшую пользу от данного раздела, убедитесь, что вы четко сформулировали свой вопрос и привели точные данные о конфигурации компьютера, а так же указали версию драйвера, версию ОС и версию ядра.
При проблемах с железом желательно указывать вывод комманд lspci, lsusb и dmesg (запускать под root-ом), содержимое соответствующих логов (лежат в /var/log) и конфигурационных файлов (лежат в /etc).
Чем больше информации мы получим, тем быстрее сможем помочь Вам.

  • Вы должны соблюдать правила форума.
  • Помните: какой вопрос, такой и ответ. Прежде чем задать вопрос прочитайте вот эту статью на форуме CIT.
  • Оскорблять запрещается.
  • Религиозные войны в Религиозных войнах.
  • Общение «просто так» в Клубе юнуксоидов. В отличие от многих других разделов, здесь разрешается сдержанно оффтопить и юморить в тему.

За интересные статьи, находки, решения, программы и просто реальную помощь будут ставиться + в репу).

В данный момент этот раздел модерируют nerezus, nickless, powerfox, pythonwin, Imple и ZeeLax. Если вы хотите помочь нам, пишите в ПМ и мы обсудим.


Спасибо. И use UNIX or die; С уважением, nerezus, nickless, powerfox, pythonwin, Imple, ZeeLax.

 

0 Пользователей читают эту тему (0 Гостей и 0 Скрытых Пользователей)
0 Пользователей:
« Предыдущая тема | *NIX и Hardware | Следующая тема »

Понравилась статья? Поделить с друзьями:
  • Syntax error near unexpected token elif
  • Syntax error near unexpected token done bash
  • Syntax error missing parentheses in call to print ошибка
  • Syntax error missing operator in query expression
  • Syntax error last token seen t garbled time