On Mon, Jun 14, 2010 at 6:18 AM, Mike Frysinger <vap...@gentoo.org> wrote: > On Sun, Jun 13, 2010 at 6:27 AM, Tomek CEDRO wrote: >> I get following build error [1] when building latest (1782 and 1783) >> trunks. Is this a known issue? > > you seem to be the only one building for *bsd systems
It is very kind of you to care so much about OS of my choice, but you are wrong. >> How this can be avoided? > > fix the problematic source ? Briliant advice. Very helpful. >> Making all in src/apps/jtag >> gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../../.. >> -I../../../include/urjtag -DLOCALEDIR=\"/usr/local/share/locale\" >> -I../../.. -I../../../include -I/usr/local/include >> -I/usr/local/include -Wall -Wmissing-prototypes -Wstrict-prototypes >> -Wpointer-arith -g -O2 -MT jtag.o -MD -MP -MF .deps/jtag.Tpo -c -o >> jtag.o jtag.c >> mv -f .deps/jtag.Tpo .deps/jtag.Po >> /bin/sh ../../../libtool --tag=CC --mode=link gcc -std=gnu99 -Wall >> -Wmissing-prototypes -Wstrict-prototypes -Wpointer-arith -g -O2 -o >> jtag jtag.o ../../../src/liburjtag.la /usr/local/lib/libintl.so >> -L/usr/local/lib /usr/local/lib/libiconv.so -Wl,-rpath >> -Wl,/usr/local/lib -L/usr/local/lib -lftdi -lusb -lreadline >> libtool: link: gcc -std=gnu99 -Wall -Wmissing-prototypes >> -Wstrict-prototypes -Wpointer-arith -g -O2 -o .libs/jtag jtag.o >> /usr/local/lib/libintl.so /usr/local/lib/libiconv.so -Wl,-rpath >> -Wl,/usr/local/lib ../../../src/.libs/liburjtag.so -L/usr/local/lib >> -lm /usr/local/lib/libftdi.so -lusb -lreadline -Wl,-rpath >> -Wl,/usr/local/lib >> ../../../src/.libs/liburjtag.so: undefined reference to `WEXITSTATUS' >> ../../../src/.libs/liburjtag.so: undefined reference to `WIFEXITED' > > because you disabled werror and truncated the log, this doesnt show > the actual problematic source file It's right in front of you, if you read the last two lines - WEXITSTATUS and WIFEXITED are undefined. In the trunk root Ive tried to find them with "grep -R", and it turned out that these are macros used in "src/cmd/cmd_cfin.c", but they are not defined anywhere. Are these macros OS specific? I have disabled the -Werror because it produced an error in parport/ppi.c (line 230) : ppi_connect, return from incompatible pointer type (this is another issue). It is possible to use configure --disable-lowlevel to have -Werror enabled, then you will get implict declaration of 'WIFEXITED' and 'WEXITSTATUS' warning in cmd_bfin.c lines 321,323, ending with error if you prefer this way. The question is - where are the WEXITSTATUS and WIFEXITED defined? Regards, Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ UrJTAG-development mailing list UrJTAG-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/urjtag-development
