Summary: | net-im/licq-1.3.5-r1 fails with libtool-2.2.4 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Matthias Schwarzott <zzam> |
Component: | New packages | Assignee: | Gentoo Net-im project <net-im> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | lordcris, polynomial-c |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 212763 |
Description
Matthias Schwarzott
2008-07-04 18:24:18 UTC
Could you please add from build log the whole src_unpack phase ? But I think this is another case of the 'brilliant' way some KDE descendants used autotools - namely this automake rule: $(top_srcdir)/acinclude.m4: $(top_srcdir)/acinclude.m4.in $(top_srcdir)/admin/acinclude.m4.in $(top_srcdir)/admin/libtool.m4.in @cd $(top_srcdir) && cat acinclude.m4.in admin/acinclude.m4.in admin/libtool.m4.in > acinclude.m4 It's effect is that libtool.m4 landed in acinclude.m4 and when eautoreconf updates ltmain.sh, it can't update libtool macro, as the old version in acinclude.m4 can't be overridden. (In reply to comment #1) > Could you please add from build log the whole src_unpack phase ? Here is it: >>> Unpacking source... >>> Unpacking licq-1.3.5.tar.bz2 to /var/tmp/portage/net-im/licq-1.3.5-r1/work * Applying licq-1.3.5-logonfix.patch ... [ ok ] * Applying licq-1.3.5-prevent-dos.patch ... [ ok ] * Applying licq-1.3.5-gcc43.patch ... [ ok ] * Applying 1.3.0-suse_bool.patch ... [ ok ] * Setting kde plugin as default ... [ ok ] * Running eautoreconf in '/var/tmp/portage/net-im/licq-1.3.5-r1/work/licq-1.3.5/plugins/msn' ... * Running aclocal ... [ ok ] * Running libtoolize --copy --force --install --automake ... [ ok ] * Running aclocal ... [ ok ] * Running autoconf ... [ ok ] * Running autoheader ... [ ok ] * Running automake --add-missing --copy --foreign ... [ ok ] * Running elibtoolize in: licq-1.3.5/admin * Applying sed-1.5.6.patch ... * Running eautoreconf in '/var/tmp/portage/net-im/licq-1.3.5-r1/work/licq-1.3.5/plugins/auto-reply' ... * Running aclocal ... [ ok ] * Running libtoolize --copy --force --install --automake ... [ ok ] * Running aclocal ... [ ok ] * Running autoconf ... [ ok ] * Running autoheader ... [ ok ] * Running automake --add-missing --copy --foreign ... [ ok ] * Running eautoreconf in '/var/tmp/portage/net-im/licq-1.3.5-r1/work/licq-1.3.5/plugins/email' ... * Running aclocal ... [ ok ] * Running libtoolize --copy --force --install --automake ... [ ok ] * Running aclocal ... [ ok ] * Running autoconf ... [ ok ] * Running autoheader ... [ ok ] * Running automake --add-missing --copy --foreign ... [ ok ] >>> Source unpacked. Looks like I'm right. Just in case, check your build log for “missing --run”, but if you don't see any, my description of the problem is complete. the only way to fix that is to recreate every acinclude.m4 in a dir where eautoreconf was run, using the same procedure it was created in the first place, just omitting admin/libtool.m4.in. To make it clear, it has to be recreated BEFORE eautoreconf is run. + 05 Jul 2008; Peter Alfredsen <loki_val@gentoo.org> licq-1.3.5-r1.ebuild: + Fix for libtool-2.2 wrt bug #230780. Thanks to Rafał Mużyło + <galtgendo@o2.pl>. + |