x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I./src -Wall -Wwrite-strings -Werror -march=native -O2 -g0 -pipe -D_FORTIFY_SOURCE=2 -fstack-protector-all -fwrapv -fPIE --param ssp-buffer-size=1 -fno-strict-aliasing -fno-strict-overflow -c -o container.o `test -f 'src/container.c' || echo './'`src/container.c
Almost all work related to tor is using -Werror. It has become part of their culture. I understand the disadvantages, namely that tommorrow's warnings will become errors, but to remove -Werror from all their m4 macros (not just obfsproxy but tor too, and probably others) would mean maintaining lots of patches and running lots of eautorconfs. I suggest keeping this bug open as a reminder, but not having it block stabilizations. Since I maintain almost all tor related projects, I'm also aware of this issue and will keep my eyes out. My guess is, if you do hit it, it will be on bumping gcc.
okay i fixed this in obfsproxy-0.1.4-r1
