Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#57084 - [libfm] build of package fails
Attached to Project:
Community Packages
Opened by Erich Eckner (deepthought) - Saturday, 13 January 2018, 12:38 GMT
Last edited by Balló György (City-busz) - Saturday, 13 January 2018, 14:25 GMT
Opened by Erich Eckner (deepthought) - Saturday, 13 January 2018, 12:38 GMT
Last edited by Balló György (City-busz) - Saturday, 13 January 2018, 14:25 GMT
|
DetailsDescription:
the build fails during configure in build() with: libtool: Version mismatch error. This is libtool 2.4.2 Debian-2.4.2-1.11, but the libtool: definition of this LT_INIT comes from libtool 2.4.6.40-6ca5-dirty. libtool: You should recreate aclocal.m4 with macros from libtool 2.4.2 Debian-2.4.2-1.11 libtool: and run autoconf again. make[4]: *** [Makefile:536: libfmactions_la-action.lo] Error 63 Additional info: * package version(s) libfm 1.2.5-1 (git revision 37952667913642f93f0322d466de41ab02850dd6) * config and/or log files etc. full log is attached Steps to reproduce: > extra-x86_64-build 
log
(31 KiB)
|
This task depends upon
Closed by Balló György (City-busz)
Saturday, 13 January 2018, 14:25 GMT
Reason for closing: Fixed
Additional comments about closing: in trunk and in the repos
Saturday, 13 January 2018, 14:25 GMT
Reason for closing: Fixed
Additional comments about closing: in trunk and in the repos
Comment by Balló György (City-busz) -
Saturday, 13 January 2018, 13:06 GMT
Strange, because it doesn't happen for me. I put an 'autoreconf' to prepare(), which should solve the problem I think.
Comment by Erich Eckner (deepthought) -
Saturday, 13 January 2018, 13:08 GMT
yeah, it's really strange: The issue popped up on archlinux32 on one buildslave, but others built the package flawless. I just checked the log, tried to build for x86_64 and the error appeared, too.