At 02:50 AM 2001/6/7 +0200, you wrote:
> > > A workaround is to either use the system libtool instead of the
> > > package's (or uninstall libtool completely) or to apply the following
> patch:
> > >
>=I just found that the problem does not exist when I run './configure' instead
>of '%configure', thereby not running libtoolize. Could it be that the
>libtoolize in the %configure macro does not what it was put in for?
If gtk+2 was bundling libtool 1.3, then the result would be what you see,
since libtool/ltmain.sh won't be replaced with 1.4 version and hence won't
complain. But I'm not so sure though, since I have never compiled gtk+2
before. Anybody care to enlighten us on this?
Abel
