Proxmark / proxmark3

Proxmark 3
http://www.proxmark.org/
GNU General Public License v2.0
3.11k stars 904 forks source link

issue compiling proxmark3 on Arch Linux #179

Closed ikarus23 closed 8 years ago

ikarus23 commented 8 years ago

Hi, I have trouble to compile the code using Arch Linux.

arm-none-eabi-gcc -c -I../include -I../common -Wall -Werror -pedantic -std=c99 -Os -DWITH_ISO14443a_StandAlone -DWITH_LF -DWITH_ISO15693 -DWITH_ISO14443a -DWITH_ISO14443b -DWITH_ICLASS -DWITH_LEGICRF -DWITH_HITAG  -DWITH_CRC -DON_DEVICE -DWITH_HFSNOOP -fno-strict-aliasing -ffunction-sections -fdata-sections -DZ_SOLO -DZ_PREFIX -DNO_GZIP -DZLIB_PM3_TUNED -I../zlib -I. -mthumb -mthumb-interwork -o obj/start.o start.c 
In file included from /usr/arm-none-eabi/include/sys/types.h:60:0,
                 from /usr/arm-none-eabi/include/stdio.h:48,
                 from ../include/hitagS.h:13,
                 from apps.h:19,
                 from start.c:13:
/usr/arm-none-eabi/include/sys/_stdint.h:31:19: error: conflicting types for 'int32_t'
 typedef __int32_t int32_t ;
                   ^
In file included from ../include/usb_cmd.h:21:0,
                 from ../include/proxmark3.h:17,
                 from start.c:12:
./stdint.h:16:18: note: previous declaration of 'int32_t' was here
 typedef int      int32_t;
                  ^
In file included from /usr/arm-none-eabi/include/sys/types.h:60:0,
                 from /usr/arm-none-eabi/include/stdio.h:48,
                 from ../include/hitagS.h:13,
                 from apps.h:19,
                 from start.c:13:
/usr/arm-none-eabi/include/sys/_stdint.h:32:20: error: conflicting types for 'uint32_t'
 typedef __uint32_t uint32_t ;
                    ^
In file included from ../include/usb_cmd.h:21:0,
                 from ../include/proxmark3.h:17,
                 from start.c:12:
./stdint.h:21:24: note: previous declaration of 'uint32_t' was here
 typedef unsigned int   uint32_t;
                        ^
../common/Makefile.common:81: recipe for target 'obj/start.o' failed

It is not the first time we have this kind of issue within the proxmark3 code (see https://github.com/Proxmark/proxmark3/issues/116). Does anyone of you know what import is causing the trouble this time?

ikarus23 commented 8 years ago

Fixed. Most likely since 39d56ec88be1ee4c8d13f1a08aa40daccab273d6. Thank you.