Benjamin Schmidt wrote:
> Hello,
> 
> I'm trying to build on GCC 4.4.0 on Linux.
> 
> building stops with following error:
> 
> libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -
> I../../src/server -I../../src/target 
> -DPKGDATADIR=\"/usr/local/share/openocd\" 
> -DPKGLIBDIR=\"/usr/local/lib/openocd\" -g -O2 -Wall -Wstrict-prototypes -
> Wformat-security -Wextra -Wno-unused-parameter -Wbad-function-cast -Wcast-
> align -Wredundant-decls -Werror -MT libhelper_la-jim.lo -MD -MP -MF 
> .deps/libhelper_la-jim.Tpo -c jim.c  -fPIC -DPIC -o .libs/libhelper_la-jim.o
> cc1: warnings being treated as errors
> jim.c: In function ‘Jim_DictKeysVector’:
> jim.c:5922: error: ‘objPtr’ may be used uninitialized in this function
> make[3]: *** [libhelper_la-jim.lo] Error 1
> make[3]: Leaving directory `/home/demonk/openocd-head/src/helper'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/home/demonk/openocd-head/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/demonk/openocd-head'
> make: *** [all] Error 2
> 
> 
> Is this a known issue?
> 
> 
> Benjamin Schmidt

I've seen similar things on u9.04 with gcc 4.4. Think it is more 
pedantic on warnings. Compiling gcc really gets stopped by this. I have 
gotten around this by
set CFLAGS=-Wno-error
./configure

I think you can also do just
./configure --disable-werror

This avoids having to touch the source code until it is fixed by the 
experts (which I am not).

-gene

_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to