On Sat 19 Feb 2011 15:07, Bruno Haible <[email protected]> writes:
> Hi,
>
> After guile-2.0.0 is installed using gcc, the installed file
> $LIBDIR/pkgconfig/guile-2.0.pc contains a line such as
>
> Cflags: -I${pkgincludedir}/2.0 -Wall -I$LIBUNISTRING_PREFIX/include
> -pthread -I$GC_PREFIX/include
The template is:
Cflags: -I${pkgincludedir}/@GUILE_EFFECTIVE_VERSION@ @GUILE_CFLAGS@
@BDW_GC_CFLAGS@
In my copy I have:
Cflags: -I${pkgincludedir}/2.0 -pthread
And in configure.ac I have:
GUILE_CFLAGS="$CPPFLAGS $PTHREAD_CFLAGS"
You said that you configured like this:
./configure --host=x86_64-pc-linux-gnu \
--prefix=/arch/x86_64-linux/gnu-inst-guile/2.0.0 \
--libdir=/arch/x86_64-linux/gnu-inst-guile/2.0.0/lib64 \
CPPFLAGS=-Wall \
--with-libunistring-prefix=/arch/x86_64-linux/gnu-inst-libunistring/0.9.3
So it is the CPPFLAGS making it there.
I would just remove CPPFLAGS entirely, but it seems to be used to
communicate libunistring compilation flags to other parts of the build.
Ludo do you have any thoughts on this?
Thanks for the report,
Andy
--
http://wingolog.org/
