Well `--disable-Werror' make it. Thanks! Rottmann, are you going to patch the code on the GIT repository?
El mié, 02-06-2010 a las 21:29 +0200, Andreas Rottmann escribió: > Romel Sandoval <[email protected]> writes: > > > After configure while trying to build I got this: > > > > .. > > Making all in g-wrap > > make[2]: se ingresa al directorio `/home/romel/src/g-wrap/g-wrap' > > make all-am > > make[3]: se ingresa al directorio `/home/romel/src/g-wrap/g-wrap' > > /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > > -I.. -I.. -I/home/romel/usr/include > > -I/home/romel/usr/include/guile/2.0 -g -O2 -Wall -Wmissing-prototypes > > -Werror -std=gnu99 -MT core-runtime.lo -MD -MP > > -MF .deps/core-runtime.Tpo -c -o core-runtime.lo core-runtime.c > > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. > > -I/home/romel/usr/include -I/home/romel/usr/include/guile/2.0 -g -O2 > > -Wall -Wmissing-prototypes -Werror -std=gnu99 -MT core-runtime.lo -MD > > -MP -MF .deps/core-runtime.Tpo -c core-runtime.c -fPIC -DPIC > > -o .libs/core-runtime.o > > cc1: warnings being treated as errors > > core-runtime.c: In function ‘gw_raise_error’: > > core-runtime.c:55: error: ignoring return value of ‘vasprintf’, declared > > with attribute warn_unused_result > > > Could you try the attached patch? It should fix this issue. As noted by > Andy Wingo, you can also use `--disable-Werror' when running configure. > > Regards, Rotty
