Open GoogleCodeExporter opened 9 years ago
Which platform, compiler and version are you using?
Is it better if you change line 31?
struct supported_tag supported_tags[] = {
=>
struct supported_tag supported_tags[11] = {
Original comment by yob...@gmail.com
on 3 Apr 2014 at 11:58
BTW libfreefare bugs should be filed there:
https://code.google.com/p/libfreefare/issues/list
Original comment by yob...@gmail.com
on 3 Apr 2014 at 12:00
Am compiling libfreefare for arm architecture using yoctotoolchain
libfreefare taken from https://code.google.com/p/libfreefare/
libnfc version 1.7.0
Original comment by sathyapr...@gmail.com
on 3 Apr 2014 at 12:10
Now am getting this error.....
make all-recursive
make[1]: Entering directory `/home/elinux1/projects/tools/libfreefare.old'
Making all in contrib
make[2]: Entering directory
`/home/elinux1/projects/tools/libfreefare.old/contrib'
Making all in libutil
make[3]: Entering directory
`/home/elinux1/projects/tools/libfreefare.old/contrib/libutil'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory
`/home/elinux1/projects/tools/libfreefare.old/contrib/libutil'
make[3]: Entering directory
`/home/elinux1/projects/tools/libfreefare.old/contrib'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory
`/home/elinux1/projects/tools/libfreefare.old/contrib'
make[2]: Leaving directory
`/home/elinux1/projects/tools/libfreefare.old/contrib'
Making all in libfreefare
make[2]: Entering directory
`/home/elinux1/projects/tools/libfreefare.old/libfreefare'
CC freefare.lo
/bin/sh: ../depcomp: No such file or directory
make[2]: *** [freefare.lo] Error 127
make[2]: Leaving directory
`/home/elinux1/projects/tools/libfreefare.old/libfreefare'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/elinux1/projects/tools/libfreefare.old'
make: *** [all] Error 2
Original comment by sathyapr...@gmail.com
on 3 Apr 2014 at 12:22
depcomp should have been provided by your autotools.
Typically a symbolic link to your autotools is created when you first run
autoreconf -vis
Original comment by yob...@gmail.com
on 3 Apr 2014 at 12:27
yes i followed that step before configuring .....
Original comment by sathyapr...@gmail.com
on 4 Apr 2014 at 4:11
Again am getting the same error.How to fix this?
Original comment by sathyapr...@gmail.com
on 8 Apr 2014 at 11:41
Original issue reported on code.google.com by
sathyapr...@gmail.com
on 3 Apr 2014 at 11:17