ARMv6 Compatibility?

[ianhyzy]

I've tried compiling this on the raspberry pi, but I get the following issues. Apologies if any of this is dumb mistakes, I don't normally compile things.

with ./configure:

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 how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -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 minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking build system type... armv6l-unknown-linux-gnueabihf
checking host system type... armv6l-unknown-linux-gnueabihf
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 for style of include used by make... GNU
checking how to create a pax tar archive... gnutar
checking dependency style of gcc... gcc3
checking whether make supports nested variables... yes
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking for gcc option to accept ISO C99... -std=gnu99
checking whether gcc -std=gnu99 and cc understand -c and -o together... yes
checking whether ln -s works... yes
checking for ar... ar
checking the archiver (ar) interface... ar
./configure: line 5446: syntax error near unexpected token `2.2'
./configure: line 5446: `LT_PREREQ(2.2)'

with ./autogen.sh:

libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `build-aux'.
libtoolize: linking file `build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: linking file `m4/libtool.m4'
libtoolize: linking file `m4/ltoptions.m4'
libtoolize: linking file `m4/ltsugar.m4'
libtoolize: linking file `m4/ltversion.m4'
libtoolize: linking file `m4/lt~obsolete.m4'
configure.ac:35: error: possibly undefined macro: PKG_CHECK_VAR
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
autoreconf: /usr/bin/autoconf failed with exit status: 1

Is this a bug? Or am I just doing something wrong? I have bluez 5.23 installed (compiled from source).

[jkuner]

Try installing pkgconf apt-get install pkgconf (as root, use sudo if you need)

You'll also need the python headers if you don't have them. sudo apt-get install python-dev

[mitras2]

@ianhyzy I was able to compile the xwiimote-bindings on my RasPi B+ on ArchLinux. Do you still need to compile this package on your RasPi? Or did the hint from @jkuner help?

[ianhyzy]

@mitras2 It's been a few months since I've used it but I believe the hint from @jkuner did work.

[mitras2]

@ianhyzy Thanks for the answer. Good to hear @jkuner 's suggestion did help. Maybee it would be cool to mark the issue as solved or closed.

Kindest regards mitras2