On 26 May 2011 20:35, Freddie Chopin <[email protected]> wrote: > 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... Hi, not a solution but perhaps a workaround, launch the ./configure with the "--disable-werror" option. As you can see in the error message "cc1: warnings being treated as errors" so the previous configure option will disable the gcc -Werror flag.
Regards; -- Luc _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
