I will try again today, but esterday I compiled openocd d2xx on cygwin
and on mingw for 32bits and 64bits without any error. Everything fine !
Note: the problem we meet during April is now gone -> thank you Spencer
Oliver.
Regards,
Laurent
http://www.amontec.com
http://www.amontec.com/jtagkey.shtml
Amontec JTAGkey-2 High-Speed USB JTAG - 1.4V to 5.5V IOS - RTCK support
Hi!
I'm trying to compile new OpenOCD source (from git) in my
crosscompilation setup but I see these errors:
>/ /../../src/rtos/'`rtos.c
/>/ libtool: compile: i686-w64-mingw32-gcc -std=gnu99 -DHAVE_CONFIG_H -I.
-I../../../src/rtos -I../.. -I../../../src -I../../src
-DPKGDATADIR=\"/usr/local/share/openocd\" -I../../../jimtcl -I../../jimtcl
-Wno-sign-compare -g -O2 -D__USE_MINGW_ANSI_STDIO -Wall -Wstrict-prototypes
-Wformat-security -Wshadow -Wextra -Wno-unused-parameter -Wbad-function-cast -Wcast-align
-Wredundant-decls -Werror -MT librtos_la-rtos.lo -MD -MP -MF .deps/librtos_la-rtos.Tpo -c
../../../src/rtos/rtos.c -o librtos_la-rtos.o
/>/ cc1: warnings being treated as errors
/>/ ../../../src/rtos/rtos.c: In function ‘gdb_thread_packet’:
/>/ ../../../src/rtos/rtos.c:147: error: unknown conversion type character ‘l’
in format
/>/ ../../../src/rtos/rtos.c:147: error: too many arguments for format
/>/ ../../../src/rtos/rtos.c:223: error: unknown conversion type character ‘l’
in format
/>/ ../../../src/rtos/rtos.c:223: error: too many arguments for format
/>/ ../../../src/rtos/rtos.c:320: error: unknown conversion type character ‘l’
in format
/>/ ../../../src/rtos/rtos.c:320: error: format ‘%s’ expects type ‘char *’, but
argument 3 has type ‘int64_t *’
/>/ ../../../src/rtos/rtos.c:320: error: too many arguments for format
/>/ ../../../src/rtos/rtos.c:473: error: unknown conversion type character ‘l’
in format
/>/ ../../../src/rtos/rtos.c:473: error: too many arguments for format
/>/ ../../../src/rtos/rtos.c:497: error: unknown conversion type character ‘l’
in format
/>/ ../../../src/rtos/rtos.c:497: error: too many arguments for format
/
Any hints for solving that? Should I try to use a different setup for
compiling OpenOCD for Windows (both 32- and 64-bit) - if yes, what do
you use? Currently I use i686-w64-mingw32 and x86_64-w64-mingw32 - is
there a better option using up-to-date compilers? I had to comment out
"dlerror" definition in jim-win32compat.h but that was simple to fix.
The sscanf()s that cause errors look pretty wild...
Thx for help!
4\/3!!
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
