problem building g-wrap

Vassili Dzuba vassilidzuba at
Thu Jan 2 09:42:09 PST 2003


I'm trying to build g-wrap using the book instructions.
I get an error message :

make[2]: Entering directory `/usr/src/g-wrap-1.2.1/test'
LD_LIBRARY_PATH=/usr/src/g-wrap-1.2.1/test/..:/usr/src/g-wrap-1.2.1/test/..: \
guile -c \
          "(set! %load-path (cons \""/usr/src/g-wrap-1.2.1/test/.."\" %load-path)) \
           (use-modules (g-wrap)) \
           (primitive-load \"./gw-test-parent-spec.scm\") \
           (gw:generate-module \"gw-test-parent\")"
source='gw-test-parent.c' object='gw-test-parent.lo' libtool=yes \
depfile='.deps/gw-test-parent.Plo' tmpdepfile='.deps/gw-test-parent.TPlo' \
depmode=gcc3 /bin/sh ../depcomp \
/bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I..     -O2 -Werror -Wall -g -I../libruntime-guile -g -O2 -I/usr/include -c -o gw-test-parent.lo `test -f gw-test-parent.c || echo './'`gw-test-parent.c
mkdir .libs
gcc -DHAVE_CONFIG_H -I. -I. -I.. -O2 -Werror -Wall -g -I../libruntime-guile -g -O2 -I/usr/include -c gw-test-parent.c -MT gw-test-parent.lo -MD -MP -MF .deps/gw-test-parent.TPlo  -fPIC -DPIC -o .libs/gw-test-parent.lo
cc1: changing search order for system directory "/usr/include"
cc1:   as it has already been specified as a non-system directory
make[2]: *** [gw-test-parent.lo] Error 1
make[2]: Leaving directory `/usr/src/g-wrap-1.2.1/test'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/g-wrap-1.2.1'
make: *** [all] Error 2

The file test/Makefile contains :

#BEGIN TEMP JUNK ============================================================
CFLAGS = -O2 -Werror -Wall -g -I../libruntime-guile -g -O2 -I/usr/include

and it seems that the final "-I/usr/include" at the end of the CFLAGS
definition is the culprit. If I remove it, the compilation works successfully

Of course, the Makefile is generated, and i don't know enough
about automake to understand it(s origin.

Has somebody an idea ?

Vassili Dzuba
Unsubscribe: send email to listar at
and put 'unsubscribe blfs-dev' in the subject header of the message

More information about the blfs-dev mailing list