On Tue, Jul 18, 2006 at 06:45:40AM +0200, Mike Hommey <[EMAIL PROTECTED]> wrote: > On Tue, Jul 18, 2006 at 01:06:39AM +0200, Nicolas Boullis <[EMAIL PROTECTED]> > wrote: > > Hi, > > > > On Mon, Jul 17, 2006 at 07:45:03PM +0200, Mike Hommey wrote: > > > > > > > > This is clearly related to #374017; the fix to this bug was incomplete. > > > > It causes FTBFS in packages that build-depend on libxml2-dev but not > > > > zlib1g-dev|libz-dev, and that use libtool. (See for example #378374.) > > > > > > In the meanwhile, I remembered that libxslt, that I built with the new > > > libxml2 to verify the changes to libxml2-dev dependencies don't break > > > everything, also uses libtool. So, wondering what was the matter, I also > > > remembered libxslt is autoreconfed. > > > > > > To solve the problem, then, all you have to do is relibtoolize your > > > package. This can be achieved by running autoreconf. You will need > > > libtool, autoconf2.13 and automake1.9. That solves the issue much better > > > than adding useless build-dep AND dependency on zlib. > > > > To be honnest, I know very little about libtool (and only little more > > abour automake and autoconf), so I tried to "autoreconf" my package... > > Unfortunately, it did not make any difference, and I can't understand > > why you would expect that "relibtoolizing" ou "autoreconfing" the > > application can fix anything if the problem actually is in > > /usr/lib/libxml2.la ... > > Because libtool in sid does the right thing when it is configured the > proper way. I did try to autoreconf vcdimager and build it, and it > works. > Check the ltmain.sh for the version number, if it doesn't contain > "debian" then try autoreconf -f.
Erf, that was libtoolize -c -f. And you need to re-run autoreconf after that. Cheers Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
