GNOME 2.0 libs not DESTDIR safe (?)


I came across a general installation problem with at least the glib, pango
and gtk+ libraries. If you configure these with eg.

  ./configure --prefix=/usr

and after this do a

  make DESTDIR=/var/tmp install

the installation spit out some errors and warnings about relinking
libraries. The result is that most of the libs get not installed in

For example the gmodule library in glib:

make[2]: Entering directory `/usr/opt/ngnome2/cvs/glib/gmodule'
/bin/sh ../mkinstalldirs /var/tmp/glib//usr/lib
/bin/sh ../libtool  --mode=install /home/jens/bin/install -c /var/tmp/glib//usr/lib/
libtool: install: warning: relinking `'
cd /opt/ngnome2/cvs/glib/gmodule; /bin/sh ../libtool --mode=relink gcc -g
-O2 -Wall -D_REENTRANT -o -rpath /usr/lib -rdynamic
-version-info 7:0:0 -export-dynamic gmodule.lo -ldl ../glib/
gcc -shared  gmodule.lo  -ldl -L/usr/lib -lglib-1.3   -Wl,-soname
-Wl, -o .libs/
/usr/i486-suse-linux/bin/ld: cannot find -lglib-1.3
collect2: ld returned 1 exit status
libtool: install: error: relink `' with the above command
before installing it
libtool: install: warning: remember to run `libtool --finish /usr/lib'
/bin/sh ../mkinstalldirs /var/tmp/glib//usr/include/glib-2.0
 /home/jens/bin/install -c -m 644 gmodule.h
make[2]: Leaving directory `/usr/opt/ngnome2/cvs/glib/gmodule'

I am using autoconf-2.52, automake 1.4-p1 and libtool-1.4a-martin which I
got from a bootstrap script.

Maybe this is only a problem on my system due to wrong installed or not up
to date build tools. But I've tested out a lot so far and couldn't fix
this. Please, can anybody try this out on his system if it works there?
And if so, mail me the autoconf/automake/libtool versions he use?

If you wonder why the hell someone want to use the DESTDIR var: well we
need this setup if we want to provide (S)RPMs for these packages.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]