Windows Client Compile Issues

dlsec · 2014-02-04 13:45:07

Hi

Im following the "ProxMarkIII - Windows 7 GSG v1.pdf" guide.

I got to section 2 (Run the Proxmark software – “./client/proxmark3.exe”.) and realised that there isnt a proxmark3.exe. So somehow i missed the compile section the guide? Checked doesnt seem to be one.

none the less, after executing make clean && make all, I had loads of arm-eabi-gcc errors: command not found.

After quite a bit of google found that removing the -none from the common make file is meant to fix this.

So I did just that, but now im getting

make -C bootrom clean
make[1]: Entering directory `/c/Users/Person/ProxSpace/pm3/bootrom'
rm -rf obj/*.o
rm -rf obj/*.elf
rm -rf obj/*.s19
rm -rf obj/*.map
rm -rf obj/*.d
rm -rf version.c
make[1]: Leaving directory `/c/Users/Person/ProxSpace/pm3/bootrom'
make -C armsrc clean
make[1]: Entering directory `/c/Users/Person/ProxSpace/pm3/armsrc'
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
rm -rf obj/*.o
rm -rf obj/*.elf
rm -rf obj/*.s19
rm -rf obj/*.map
rm -rf obj/*.d
rm -rf version.c
make[1]: Leaving directory `/c/Users/Person/ProxSpace/pm3/armsrc'
make -C client clean
make[1]: Entering directory `/c/Users/Person/ProxSpace/pm3/client'
rm -f cli cli.exe flasher flasher.exe proxmark3 proxmark3.exe snooper snooper.
e obj/nonce2key/crapto1.o obj/nonce2key/crypto1.o obj/nonce2key/nonce2key.o ob
mifarehost.o obj/crc16.o obj/iso14443crc.o obj/iso15693tools.o obj/data.o obj/
aph.o obj/ui.o obj/cmddata.o obj/cmdhf.o obj/cmdhf14a.o obj/cmdhf14b.o obj/cmd
15.o obj/cmdhfepa.o obj/cmdhflegic.o obj/cmdhficlass.o obj/cmdhfmf.o obj/cmdhw
obj/cmdlf.o obj/cmdlfhid.o obj/cmdlfem4x.o obj/cmdlfhitag.o obj/cmdlfti.o obj
mdparser.o obj/cmdmain.o obj/cmdlft55xx.o obj/cmdlfpcf7931.o obj/pm3_binlib.o
j/scripting.o obj/cmdscript.o obj/pm3_bitlib.o obj/*.o *.o *.moc.cpp
cd ../liblua && make clean
make[2]: Entering directory `/c/Users/Person/ProxSpace/pm3/liblua'
rm -f liblua.a lua luac lapi.o lcode.o lctype.o ldebug.o ldo.o ldump.o lfunc.o
gc.o llex.o lmem.o lobject.o lopcodes.o lparser.o lstate.o lstring.o ltable.o
m.o lundump.o lvm.o lzio.o lauxlib.o lbaselib.o lbitlib.o lcorolib.o ldblib.o
olib.o lmathlib.o loslib.o lstrlib.o ltablib.o loadlib.o linit.o lua.o luac.o
make[2]: Leaving directory `/c/Users/Person/ProxSpace/pm3/liblua'
make[1]: Leaving directory `/c/Users/Person/ProxSpace/pm3/client'
make -C recovery clean
make[1]: Entering directory `/c/Users/Person/ProxSpace/pm3/recovery'
rm -f bootrom.bin fullimage.bin proxmark3_recovery.bin
make[1]: Leaving directory `/c/Users/Person/ProxSpace/pm3/recovery'
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
/bin/sh: arm-eabi-gcc: command not found
svn: E155021: This client is too old to work with the working copy at
'C:\Users\Person\ProxSpace\pm3' (format 31).
You need to get a newer Subversion client. For more details, see
http://subversion.apache.org/faq.html#working-copy-format-change

svn: E155021: This client is too old to work with the working copy at
'C:\Users\Person\ProxSpace\pm3' (format 31).
You need to get a newer Subversion client. For more details, see
http://subversion.apache.org/faq.html#working-copy-format-change

make[1]: arm-eabi-gcc: Command not found
make[1]: *** [obj/version.o] Error 127
make: *** [bootrom/all] Error 2
pm3 ~/ProxSpace/pm3$

Any help would be appreciated.

dlsec · 2014-02-04 13:50:18

Im running a 64bit of Windows 8.1 (just thought id mention that)

dlsec · 2014-02-05 22:31:36

Anyone

app_o1 · 2015-03-04 04:12:41

Can someone on windows, send me his "\sys\ioctl.h" ?
For cygwin64, it is located in C:\cygwin64\usr\include\sys
Thank you

marshmellow · 2015-03-04 04:44:13

https://www.sendspace.com/file/d97an9 from non 64 version

app_o1 · 2015-03-04 08:45:26

Thanks a lot.
This does not solve my problem unfortunately.

uart.c:283
The FIONREAD function is not defined anywhere.
I guess it should be defined in <sys/ioctl.h>
I found a way around by adding a definition for FIONREAD in iocth.h

Then I got an error with CMIN CTIME in util.c
I added
#define CMIN 1
#define CTIME 1
to fix the error.

Now it is IOC_OUT that is not defined anywhere...

I am clearly missing something somewhere...

app_o1 · 2015-03-04 09:53:14

I was able to compile. But the client does not work...

Here is what I added:

#define FIONREAD _IOR('f', 127, u_long)
#define _IOR(g,n,t) _IOC(IOC_OUT, (g), (n), sizeof(t))
#define IOC_OUT 0x40000000

#define CMIN 1
#define CTIME 1

What are the correct values for FIONREAD, _IOR, IOC_OUT, CMIN, CTIME ?

app_o1 · 2015-03-12 13:58:42

With a fresh installation of windows, I get much less errors.
I managed to compile the last GitHub code just by adding :

#define CMIN  1
#ifdef CTIME
#undef CTIME
#endif
#define CTIME 1

to util.c

Now that everything has been compiled. Flasher.exe does not seem to see the Proxmark on COMx

iceman · 2015-03-12 14:19:59

Maybe you need the old hid-flasher?

marshmellow · 2015-03-12 14:20:07

Windows drivers? Com port show in device manager?

app_o1 · 2015-03-12 15:12:59

Yes it is showing in the device manager. Still no results.

I tested with old flasher
New flasher
Old driver before CDC
New driver from last project
Driver from previous project
Pressing the button
Not pressing the button

Here is my client and flasher.
https://www.sendspace.com/file/naqu12

app_o1 · 2015-03-12 15:42:56

I managed to flash using flasher.exe from pm3-bin-0.0.7\win32 (client+GUI)

but the client proxmark3.exe does see my proxmark...

Last edited by app_o1 (2015-03-12 15:44:45)

iceman · 2015-03-12 16:07:18

Did you flash bootrom/ fpga / os ?? With all changes done , you'll need to do that.

app_o1 · 2015-03-12 16:19:49

I always flash all of them. (luckily I have never bricked my pm3)
I have made modification to uart.h
Even though it compiles without any error, it might not give proper results.
It might also be something with the dll
I guess I'll have to wait for asper's 0.0.8

iceman · 2015-03-12 16:35:56

When @Holiman tags a new V.2 then @Asper will make a new binary release.

marshmellow · 2015-03-13 02:19:35

My guess is your code is old compiling an old version of proxmark3.exe and flasher.exe

app_o1 · 2015-03-28 08:23:54

I m using what is on gitHub.
What I do is, I go to github and click on "Download ZIP"
https://github.com/Proxmark/proxmark3/archive/master.zip
Then I extract in C:/master and compile from here.

iceman · 2015-03-28 08:51:06

wait a moment now. do you have this issue still?

And the warning/error is: /bin/sh: arm-eabi-gcc: command not found ????

Then you need to rename it. http://www.proxmark.org/forum/viewtopic.php?id=1348

rule wrote:

Hey hey,
Most new versions of the toolchains use the new naming convention. It basically comes down in a change from
 arm-eabi-*
to
 arm-none-eabi-* 
This is for example the case for the latest devkitPro. But also the binary ones for Windows like YAGARTO.
It would be good to update the proxspace as well to be compliant with the new convention. If someone likes to construct/compile a new windows environment, please let me know.
Cheers,
Roel

Last edited by iceman (2015-03-28 08:53:03)

app_o1 · 2015-03-28 09:36:16

No that is not the problem. I have correct cross compiler installed.
The first problem appears here :

gcc -std=c99 -I. -I../include -I../common -I/opt/local/include -I../liblua -Wall  -g -O4 -c -o obj/uart.o uart.c
uart.c: In function ‘uart_receive’:
uart.c:283:46: error: ‘FIONREAD’ undeclared (first use in this function)
     res = ioctl(((serial_port_unix*)sp)->fd, FIONREAD, &byteCount);
                                              ^
uart.c:283:46: note: each undeclared identifier is reported only once for each function it appears in
Makefile:132

The only way I found to avoid this error is to add this in uart.h

  #include <asm/socket.h>

---
But then, I am getting another error :

gcc -std=c99 -I. -I../include -I../common -I/opt/local/include -I../liblua -Wall  -g -O4 -c -o obj/util.o util.c
util.c: In function ‘ukbhit’:
util.c:30:27: error: ‘CMIN’ undeclared (first use in this function)
   Ntty.c_cc[VMIN]       = CMIN;    /* minimum time to wait      */
                           ^
util.c:30:27: note: each undeclared identifier is reported only once for each function it appears in
util.c:31:27: erreur: ‘CTIME’ undeclared (first use in this function)
   Ntty.c_cc[VTIME]      = CTIME;   /* minimum characters to wait for */
                           ^

It can be avoided if I add this to util.h

#include <asm/socket.h>

---
With these changes, it compiles.
But the client does not recognize my PM3 on the correct COM port.
I am not able to flash anything.

https://www.sendspace.com/file/l1mbz0

Last edited by app_o1 (2015-03-28 09:49:32)

iceman · 2015-03-28 10:19:28

Strange, when I look inside the uart.c file, and the line your error message indicates, it is not in the WIN_32 defined.. its inside the "IFNDEF _WIN32" part.. which would be why you have and issue with compiling it on a windows machine to start with.

lalelu · 2015-04-05 14:30:17

Same issue here...

After testing with:

gcc -E -dM ui.c | find /i "win"

my system's output is:

#define __CYGWIN__ 1

so, the compiler is detecting cygwin and the #IFNDEF is not working and the compiler builds for a linux system.

..after defining the _WIN32 symbol in Eclipse the next error pops up:

util.c:42:19: fatal error: conio.h: No such file or directory

I googled this missing file, but i still have no idea in which package this file can be found...

iceman · 2015-04-05 14:36:37

I don't know but a suggestion would be to configure the correct time.c solution for a CYGWIN setup? As it is now its for iether windows or linux? In my mingw setup it works, but that is not the same a cygwin setup. Should be very similar.

lalelu · 2015-04-05 15:48:42

anyway, compiling in ProxSpace works fine for me

But I had the same issues like app_o1had when compiling in a Cygwin environment, so I think his problem must be something like that...

Proxmark3 community

Announcement

#1 2014-02-04 13:45:07

Windows Client Compile Issues

#2 2014-02-04 13:50:18

Re: Windows Client Compile Issues

#3 2014-02-05 22:31:36

Re: Windows Client Compile Issues

#4 2015-03-04 04:12:41

Re: Windows Client Compile Issues

#5 2015-03-04 04:44:13

Re: Windows Client Compile Issues

#6 2015-03-04 08:45:26

Re: Windows Client Compile Issues

#7 2015-03-04 09:53:14

Re: Windows Client Compile Issues

#8 2015-03-12 13:58:42

Re: Windows Client Compile Issues

#9 2015-03-12 14:19:59

Re: Windows Client Compile Issues

#10 2015-03-12 14:20:07

Re: Windows Client Compile Issues

#11 2015-03-12 15:12:59

Re: Windows Client Compile Issues

#12 2015-03-12 15:42:56

Re: Windows Client Compile Issues

#13 2015-03-12 16:07:18

Re: Windows Client Compile Issues

#14 2015-03-12 16:19:49

Re: Windows Client Compile Issues

#15 2015-03-12 16:35:56

Re: Windows Client Compile Issues

#16 2015-03-13 02:19:35

Re: Windows Client Compile Issues

#17 2015-03-28 08:23:54

Re: Windows Client Compile Issues

#18 2015-03-28 08:51:06

Re: Windows Client Compile Issues

#19 2015-03-28 09:36:16

Re: Windows Client Compile Issues

#20 2015-03-28 10:19:28

Re: Windows Client Compile Issues

#21 2015-04-05 14:30:17

Re: Windows Client Compile Issues

#22 2015-04-05 14:36:37

Re: Windows Client Compile Issues

#23 2015-04-05 15:48:42

Re: Windows Client Compile Issues

Board footer