--enable-static in gconfmm2.0-- is it really needed?
Hi,
I am the maintainer of the gnome2.2 backport for woody, and have tried
unsuccessfully to get the c++ bindings to compile on woody. With the
newly added gtk+2.2.2, I have actually gotten much further. I use
CC=gcc-3.0 and CXX=g++-3.0 for everything 'mm' related, however when I
get to compiling gconfmm2.0, it dies with:
make[5]: Entering directory
`/home/jstrand1/src/2.2.2/c++/foo/gconfmm2.0-2.0.1/gconf/gconfmm'
if /bin/sh ../../libtool --mode=compile g++-3.0 -DHAVE_CONFIG_H
-DG_LOG_DOMAIN=\"gconfmm\" -I../../gconf -I../../gconf -DORBIT2=1
-pthread -I/usr/include/gtkmm-2.0 -I/usr/lib/gtkmm-2.0/include
-I/usr/lib/sigc++-1.2/include -I/usr/include/sigc++-1.2
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
-I/usr/include/gconf/2 -I/usr/include/orbit-2.0
-I/usr/include/linc-1.0 -g -O2 -MT client.lo -MD -MP -MF
".deps/client.Tpo" \
-c -o client.lo `test -f 'client.cc' || echo './'`client.cc; \
then mv ".deps/client.Tpo" ".deps/client.Plo"; \
else rm -f ".deps/client.Tpo"; exit 1; \
fi
mkdir .libs
g++-3.0 -DHAVE_CONFIG_H -DG_LOG_DOMAIN=\"gconfmm\" -I../../gconf
-I../../gconf -DORBIT2=1 -pthread -I/usr/include/gtkmm-2.0
-I/usr/lib/gtkmm-2.0/include -I/usr/lib/sigc++-1.2/include
-I/usr/include/sigc++-1.2 -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -I/usr/include/gconf/2
-I/usr/include/orbit-2.0 -I/usr/include/linc-1.0 -g -O2 -MT client.lo
-MD -MP -MF .deps/client.Tpo -c client.cc -fPIC -DPIC -o
.libs/client.lo
g++-3.0 -DHAVE_CONFIG_H -DG_LOG_DOMAIN=\"gconfmm\" -I../../gconf
-I../../gconf -DORBIT2=1 -pthread -I/usr/include/gtkmm-2.0
-I/usr/lib/gtkmm-2.0/include -I/usr/lib/sigc++-1.2/include
-I/usr/include/sigc++-1.2 -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -I/usr/include/gconf/2
-I/usr/include/orbit-2.0 -I/usr/include/linc-1.0 -g -O2 -MT client.lo
-MD -MP -MF .deps/client.Tpo -c client.cc -o client.o >/dev/null 2>&1
make[5]: *** [client.lo] Error 1
make[5]: Leaving directory
`/home/jstrand1/src/2.2.2/c++/foo/gconfmm2.0-2.0.1/gconf/gconfmm'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory
`/home/jstrand1/src/2.2.2/c++/foo/gconfmm2.0-2.0.1/gconf/gconfmm'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/home/jstrand1/src/2.2.2/c++/foo/gconfmm2.0-2.0.1/gconf'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/home/jstrand1/src/2.2.2/c++/foo/gconfmm2.0-2.0.1/gconf'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/home/jstrand1/src/2.2.2/c++/foo/gconfmm2.0-2.0.1'
make: *** [build-stamp] Error 2
I noticed that --enable-static defaults to 'no' (configure --help), but
debian includes it. By getting rid of '--enable-static' it compiles
fine. Does debian policy or gnome in general need this enabled? Can I
safely leave it out?
Thanks,
Jamie
--
Email: jstrand1@rochester.rr.com
GPG/PGP ID: 26384A3A
Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A
Reply to: