Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 74184 - fam crashed when compiling with libtool 1.5.10
Summary: fam crashed when compiling with libtool 1.5.10
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: foser (RETIRED)
URL:
Whiteboard:
Keywords:
: 74168 74668 74804 75059 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-12-12 05:33 UTC by Dulmandakh
Modified: 2006-03-05 05:53 UTC (History)
12 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
modified ebuild (fam-2.7.0-r2.ebuild,2.06 KB, application/octet-stream)
2004-12-12 16:53 UTC, Christian Malerbakken
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dulmandakh 2004-12-12 05:33:28 UTC
When I try to emerge GNOME, I get error when compiling fam 2.7.0-r2. Error shows me and stops compiling.

*** Gentoo sanity check failed! ***
*** libtool.m4 and ltmain.sh have a version mismatch! ***
*** (libtool.m4 = 1.5.10, ltmain.sh = 1.4) ***

Please run:

  libtoolize --copy --force

if appropriate, please contact the maintainer of this
package (or your distribution) for help.

Reproducible: Always
Steps to Reproduce:
1. emerge fam
2. when it unpacks source archive press CTRL+Z
3. do "cd /var/tmp/portage/fam-2.7.0-r2/work/fam-2.7.0/"
4. in ltmain.sh file replace VERSION=1.4 with VERSION=1.5.10
Actual Results:  
compiled without any problem


Portage 2.0.51-r8 (default-linux/x86/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0,
2.6.9-gentoo-r1 i686)
=================================================================
System uname: 2.6.9-gentoo-r1 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz
Gentoo Base System version 1.6.7
Python:              dev-lang/python-2.3.4 [2.3.4 (#1, Dec 12 2004, 18:32:05)]
dev-lang/python:     2.3.4
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.5, 1.8.5-r2, 1.6.3, 1.7.9, 1.4_p6, 1.9.3
sys-devel/binutils:  2.15.92.0.2-r1
sys-devel/libtool:   1.5.10-r1
virtual/os-headers:  2.4.22
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-pipe -mfpmath=sse -msse2 -march=pentium4 -mtune=pentium4 -Os "
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-pipe -mfpmath=sse -msse2 -march=pentium4 -mtune=pentium4 -Os "
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks nodoc sandbox sfperms"
GENTOO_MIRRORS="http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X apm bitmap-fonts cdr crypt emacs esd fam gdbm gif gnome gtk gtk2 imlib
ithreads jpeg libg++ libwww mad ncurses nls oggvorbis opengl oss pam pdflib perl
png readline sdl spell ssl svga tcpd truetype userlocales x86 xml2 xmms zlib"
Comment 1 foser (RETIRED) gentoo-dev 2004-12-12 14:40:42 UTC
I'm not aware of any problems with the current way fam is getting built & I do not know why this has suddenly become an issue. Reassigning to those who supposedly do know & make build breaking messages for it.
Comment 2 foser (RETIRED) gentoo-dev 2004-12-12 14:41:01 UTC
*** Bug 74168 has been marked as a duplicate of this bug. ***
Comment 3 SpanKY gentoo-dev 2004-12-12 14:51:13 UTC
error message is pretty clear, fam is incorrectly running autotools

bug is not in libtool but in fam

refer to http://bugs.gentoo.org/show_bug.cgi?id=73563#c9 for more info
Comment 4 Christian Malerbakken 2004-12-12 16:53:19 UTC
Created attachment 45871 [details]
modified ebuild

This makes fam-2.7.0-r2 build, and as far as I can tell work correctly
Comment 5 Joe McCann (RETIRED) gentoo-dev 2004-12-16 13:34:46 UTC
*** Bug 74668 has been marked as a duplicate of this bug. ***
Comment 6 Andrew Gaydenko 2004-12-16 18:34:06 UTC
Have ~x86-synced few minutes ago. While emerging lirc, have got
the same error:

*** Gentoo sanity check failed! ***
*** libtool.m4 and ltmain.sh have a version mismatch! ***
*** (libtool.m4 = 1.5.10, ltmain.sh = 1.4.3) ***
Comment 7 Jure Repinc 2004-12-17 03:38:21 UTC
I'm still having the same problem.
Comment 8 Daniel Webert 2004-12-17 06:30:27 UTC
have a look at bug #74711
Comment 9 Joe McCann (RETIRED) gentoo-dev 2004-12-17 19:23:57 UTC
*** Bug 74804 has been marked as a duplicate of this bug. ***
Comment 10 Jonathan Heaney 2004-12-18 16:41:17 UTC
I'm having the same problem, the fam ebuild from comment #4 works OK here.
Comment 11 Carsten Lohrke (RETIRED) gentoo-dev 2004-12-20 08:09:07 UTC
*** Bug 75059 has been marked as a duplicate of this bug. ***
Comment 12 ferret 2004-12-21 16:06:04 UTC
media-libs/lcms-1.12 and -1.13 also break, but 1.11 doesn't.
Comment 13 ferret 2004-12-21 18:28:58 UTC
x11-themes/redhat-artwork-0.96 and x11-themes/redhat-artwork-0.120 fail, but x11-themes/redhat-artwork-0.95 doesn't.
I'm reporting these still because from looking at other bug reports thi needs fixing on a per-ebuild basis.
Comment 14 Carsten Lohrke (RETIRED) gentoo-dev 2004-12-22 04:28:42 UTC
ferret: This bug is about fam. Regarding other occurences you may notice, open new bug reports, if there is one missing, please. In case of the two you mentioned: lcms -> Bug 74442, redhat-artwork -> Bug 74729.
Comment 15 Josh Perry 2004-12-24 20:34:09 UTC
synced and still got the error, google brought me here, the attached ebuild worked however.
Comment 16 Disenchanted (RETIRED) gentoo-dev 2004-12-29 12:33:29 UTC
-r2 is fixed sync in 30 minutes
Comment 17 Richard Hartmann 2006-03-05 05:53:45 UTC
As the command

emerge --oneshot -vD =app-admin/fam-2.7.0

doesn't refuse to emerge, but fails with the error

configure: error:

*** [Gentoo] sanity check failed! ***
*** libtool.m4 and ltmain.sh have a version mismatch! ***
*** (libtool.m4 = 1.5.22, ltmain.sh = 1.4) ***

Should it be masked, so I do can't even run in this "problem"?

My solution was to emerge

fam-2.7.0-r4

manually.