libtool/ltmain.sh mismatch error

Message

noathustra · Post by **noathustra** » Mon Dec 20, 2004 1:45 pm

MOD EDIT: Making this thread sticky until these errors stop popping up all over the place... --plate Seems to have stopped. --pjp

I wanted to try out im-ja but can't compile it. I get the message:

Code: Select all

*** libtool.m4 and ltmain.sh have a version mismatch! ***
*** (libtool.m4 = 1.5.10, ltmain.sh = 1.4.3) ***

Please run:

  libtoolize --copy --force

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

When I run libtoolize I get:

Code: Select all

libtoolize: `configure.ac' does not exist

Any ideas?

plate · Post by **plate** » Mon Dec 20, 2004 11:00 pm

noathustra · Post by **noathustra** » Mon Dec 20, 2004 11:39 pm

I read the linked discussion but don't understand what to do. Is the gist that I am getting this error because the ebuild is broken? Do I need to edit the ebuild? Should I post a bug on bugzilla?

plate · Post by **plate** » Tue Dec 21, 2004 9:57 am

This sanity check showstopper has hit quite a number of ebuilds over the past few days, and you should indeed file a bug report because there isn't one about im-ja yet as far as I can see. The ebuild needs to be modified, you could probably do that for yourself and submit the patch along with your bug report.

qbic · Post by **qbic** » Tue Dec 21, 2004 10:58 am

You can do a quick hack just by puttinng libtoolize --copy --force in the ebuild.

example from lcms:

Code: Select all

src_compile() {
    libtoolize --copy --force     # adding this line will fix it for now
    econf \
        --disable-dependency-tracking \
        `use_with jpeg` \
        `use_with tiff` \
        `use_with zlib` \
        `use_with python` || die
    emake || die "emake failed"
}

Worked for me, but i still don't understand why the error shows up.

blackdog · Post by **blackdog** » Fri Dec 24, 2004 3:37 pm

How do I 'hack' the ebuild? I'm having this problem on two files. fam-2.7.0-r2 for xscreensaver and lcms-1.13 for mozilla-firefox-bin.

Thanks!

qbic · Post by **qbic** » Fri Dec 24, 2004 4:01 pm

Just edit the ebuild and add

Code: Select all

libtoolize --copy --force

before the econf line.

Example from above is from lcms-1.13.ebuild.
Cheers

blackdog · Post by **blackdog** » Fri Dec 24, 2004 6:11 pm

I don't know where I should start to edit the ebuild. That's my question. If I just nano the lcms tar file, it's all gibberish. Do I need to unpack it, edit and repack? If so, I'm really lost.

Exci · Post by **Exci** » Fri Dec 24, 2004 9:28 pm

all ebuild scripts are in /usr/portage

this particular ebuild is in /usr/portage/media-libs/lcms/

there you can edit the .ebuild files with nano

so with root

Code: Select all

nano /usr/portage/media-libs/lcms/lcms-1.13.ebuild

the bug in bugzilla

http://bugs.gentoo.org/show_bug.cgi?id=74442

qbic · Post by **qbic** » Fri Dec 24, 2004 9:29 pm

Ok, a full tutorial then

1: Edit the ebuild in question. (eg. vim /usr/portage/media-libs/lcms/lcms-1.13.ebuild)
2: Locate a line in the code that contains "econf"
3: Add a line above the "econf" line
4: Write "libtoolize --copy --force"
5: That's it, enjoy!

blackdog · Post by **blackdog** » Sat Dec 25, 2004 12:33 am

Sweet, you guys rock. Thanks for the info!

By the way, if anyone runs into this problem with fam, here's where I stuck the libtoolize line.

Code: Select all

src_unpack() {
        unpack ${A}

        cd ${S}
        # dnotify patch #43027
        epatch ${FILESDIR}/${P}-dnotify.patch

        # Fix permission problems with user* in FEATURES (#35307)
        chmod u+w ${S}/configure

        # Please do not remove this again - fixes $S and $D in libtool linker
        # scripts (.la files)

        * libtoolize --copy --force *

        cd ${S}; elibtoolize

        gnuconfig_update
}

7thSphere · Post by **7thSphere** » Sat Dec 25, 2004 2:23 pm

qbic wrote:You can do a quick hack just by puttinng libtoolize --copy --force in the ebuild.

example from lcms:
Code: Select all
src_compile() {
    libtoolize --copy --force     # adding this line will fix it for now
    econf \
        --disable-dependency-tracking \
        `use_with jpeg` \
        `use_with tiff` \
        `use_with zlib` \
        `use_with python` || die
    emake || die "emake failed"
}
Worked for me, but i still don't understand why the error shows up.

thanks! works like a charm.

Sebell · Post by **Sebell** » Wed Dec 29, 2004 5:55 pm

Greetings folks:

I ran into this error (libtool mismatch) whilst building fam during an emerge -uv world. I have a question (or two) - - the fam maintainers have stuffed in an elibtoolize statement in the ebuild and marked it to please retain ...
A) what is elibtoolize supposed to do and
B) where in portage/emerge/ebuild process is the elibtoolize function defined? --

I cant seem to find the relevant code ... and has anyone else noted that elibtoolize is missing?
I've noted that elibtoolize is called in several of the cases where this type of error is involved -- if I'm completely off topic, shoot me.

In any case, editing the relevant ebuild file and adding the libtoolize --copy --force statement as listed in this thread effectively solved my problem with the ebuild, however I wonder if something broke recently in portage/emerge/ebuild/emake/einstall (i.e. elibtoolize)

emerge ---info below:

Portage 2.0.51-r8 (default-linux/x86/2004.3, gcc-3.3.4, glibc-2.3.4.20041102-r0, 2.6.9-gentoo-r4test-2 i686)
=================================================================
System uname: 2.6.9-gentoo-r4test-2 i686 AMD Athlon(tm) Processor
Gentoo Base System version 1.6.8
Python: dev-lang/python-2.3.4 [2.3.4 (#1, Aug 31 2004, 14:41:10)]
dev-lang/python: 2.3.4
sys-devel/autoconf: 2.59-r6, 2.13
sys-devel/automake: 1.8.5-r2, 1.5, 1.4_p6, 1.6.3, 1.7.9, 1.9.3
sys-devel/binutils: 2.15.92.0.2-r2
sys-devel/libtool: 1.5.10-r2
virtual/os-headers: 2.6.8.1-r1
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -march=athlon-xp -fomit-frame-pointer -funroll-loops -frerun-loop-opt -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3.3/env/usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/bind /var/qmail/alias /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -march=athlon-xp -fomit-frame-pointer -funroll-loops -frerun-loop-opt -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms"
GENTOO_MIRRORS="ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo http://128.213.5.34/gentoo/ http://cudlug.cudenver.edu/gentoo/ http://gentoo.netnitco.net http://mirror.cpsc.ucalgary.ca/mirror/gentoo.org"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="3dnow X Xaw3d acl alsa apm arts avi berkdb bitmap-fonts cdparanoia cdr crypt cups curl dga directfb divx4linux dvd dvdr encode ethereal fam fbcon foomaticdb fortran gd gdbm gif gnome gphoto2 gpm gstreamer gtk gtk2 gtkhtml guile icq imagemagick imap imlib ipv6 jabber java joystick jpeg kde ldap lesstif libwww live mad maildir mbox mikmod mmx mng motif mozilla mpeg msn mysql ncurses network nls oggvorbis opengl oscar oss pam pda pdflib perl png pnp povray ppds python qt quicktime readline rtc samba scanner sdl slang slp socks5 speex spell sse ssh ssl svga tcltk tcpd tiff truetype usb v4l2 wmf xml xml2 xmms xosd xv xvid yahoo zeo zlib video_cards_radeon"

TrueDFX · Post by **TrueDFX** » Wed Dec 29, 2004 8:46 pm

Hi,

Sebell wrote:A) what is elibtoolize supposed to do and

It patches some files that are used by a lot of packages. The patches are stored in /usr/portage/eclass/ELT-patches; it may be easier to just look over them to get the basic idea of what they do.

B) where in portage/emerge/ebuild process is the elibtoolize function defined?

It's defined in /usr/portage/eclass/libtool.eclass.

Sebell · Post by **Sebell** » Thu Dec 30, 2004 8:22 pm

Thanks for the reply TrueDFX - I've looked it over and I think I might see something in the eclass file that might be an issue. I suspect that the elibtoolize in the fam embuild failed for a specific reason, but I need to do more reading through the overall process.

TrueDFX · Post by **TrueDFX** » Thu Dec 30, 2004 11:04 pm

Why do you say elibtoolize failed? You previously said that after adding libtoolize --copy --force, the installation was successful. If elibtoolize failed, wouldn't it still leave you with a broken ebuild if you add another line? It isn't supposed to be used instead of libtoolize, if that's what you're thinking.

Bob P · Post by **Bob P** » Fri Dec 31, 2004 10:28 pm

blackdog wrote:By the way, if anyone runs into this problem with fam, here's where I stuck the libtoolize line.

if anyone can help with the application of this code to the 2.7.0-r2 ebuild of fam, please read this thread.

thanks.

m0wi · Post by **m0wi** » Tue Jan 04, 2005 8:00 pm

This is also a problem with the unixOBDC ebuild.
Just add:
libtoolize --copy --force

Before/above econf.
Mainly adding this so "unixODBC" will be tagged towards this thread in a forum search.
regards,
jt

Kelvie · Post by **Kelvie** » Thu Jan 20, 2005 3:49 am

This is a very odd problem.

I have this problem every time I try to compile a simple "Hello World" program in KDevelop.

Anyone know how to solve this? I know I can just go into the project directory and run 'libtoolize --force --copy', but is there a way I can fix this so I do not have to do that EVERY time?

marcelser · Post by **marcelser** » Tue Jan 25, 2005 9:32 am

Hi,

I already edited the lcms ebuild and tried adding libtoolize --copy --force before the econf line ind src_compile function. I also tried modifying the src_unpack function which already has the libtoolize command (but without --copy --force) but I always get the following output when emerging lcms:

Code: Select all

>>> Unpacking lcms-1.13.tar.gz to /var/tmp/portage/lcms-1.13/work
 * Using GNU config files from /usr/share/libtool
 *  Updating config.sub                                                                                                                                                                                                                [ ok ]
 *  Updating config.guess                                                                                                                                                                                                              [ ok ]
 * Patching ${S}/ltmain.sh ...
 *   Applying portage-1.4.1.patch ...
 *   Applying max_cmd_len-1.5.0.patch ...
 *   Applying sed-1.4.3.patch ...
 *   Applying tmp-1.3.5.patch ...
 * Applying uClibc/libtool patches ...
 * Running autoreconf...
 * Running libtoolize...
 * Patching ${S}/ltmain.sh ...
 *   Could not apply portage.patch!
 *   Please verify that it is not needed.
 * Cannot apply any patch, running libtoolize...
 * Applying uClibc/libtool patches ...
>>> Source unpacked.

As you can see I always get the message "could not apply portage.patch" and "cannot apply any patch running libtoolize". At this point I always stop the emerge process because I don't know if this must be fixed first or if this is ok.

Can anyone tell me if I can proceed or if something is broken with my ebuild?? Thanks a lot

askoff · Post by **askoff** » Sat Jan 29, 2005 9:40 pm

Kelvie wrote:This is a very odd problem.

I have this problem every time I try to compile a simple "Hello World" program in KDevelop.

Anyone know how to solve this? I know I can just go into the project directory and run 'libtoolize --force --copy', but is there a way I can fix this so I do not have to do that EVERY time?

So do I. I made a simple C program, and it doesn't work.

Rafal_Glazar · Post by **Rafal_Glazar** » Wed Feb 02, 2005 2:35 pm

Kelvie wrote:This is a very odd problem.

I have this problem every time I try to compile a simple "Hello World" program in KDevelop.

Anyone know how to solve this? I know I can just go into the project directory and run 'libtoolize --force --copy', but is there a way I can fix this so I do not have to do that EVERY time?

After downgrading libtool from 1.5.10-r4 to 1.5.2-r7 problem was solved, so I assume libtool-1.5.10 is what causing this.

mrhodes · Post by **mrhodes** » Thu Feb 03, 2005 4:52 pm

I'm having the same problems, with kdevelop...

I'm downgrading my libtools right now.... I'll post back my results soon...

mrhodes · Post by **mrhodes** » Thu Feb 03, 2005 4:54 pm

ok... I just got this when trying to downgrade...

Code: Select all

 * Building libtool-1.3.5 ...
rm -f acinclude.m4
cp ./libtool.m4 acinclude.m4
cd . && /var/tmp/portage/libtool-1.5.2-r7/work/libtool-1.3.5/missing aclocal
/bin/sh: line 1: /var/tmp/portage/libtool-1.5.2-r7/work/libtool-1.3.5/missing: No such file or directory
make: *** [aclocal.m4] Error 127

!!! ERROR: sys-devel/libtool-1.5.2-r7 failed.
!!! Function src_compile, Line 161, Exitcode 2
!!! (no error message)
!!! If you need support, post the topmost build error, NOT this status message.

Any ideas?

mrhodes · Post by **mrhodes** » Thu Feb 03, 2005 5:13 pm

Ok... I fixed that problem, and emerged libtools 1.5.2
It works now....

Now I can finally use kdevelop again

This solved my problem with all the warnings I got when trying to build programs

Thanks for the idea to downgrade libtools

libtool/ltmain.sh mismatch error

libtool/ltmain.sh mismatch error

unixODBC

libtoolize can't apply patch