Opened 12 years ago
Closed 12 years ago
#35700 closed defect (invalid)
tesseract not building due to incorrect version of libtool
Reported by: | danieljamesbertrand@… | Owned by: | markemer (Mark Anderson) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.2 |
Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt), werner@… | |
Port: | tesseract |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
:info:build libtool: Version mismatch error. This is libtool 2.4, but the :info:build libtool: definition of this LT_INIT comes from libtool 2.4.2. :info:build libtool: You should recreate aclocal.m4 with macros from libtool 2.4 :info:build libtool: and run autoconf again. :info:build make[3]: *** [ambigs.lo] Error 63 :info:build make[3]: *** Waiting for unfinished jobs.... :info:build libtool: Version mismatch error. This is libtool 2.4, but the :info:build libtool: definition of this LT_INIT comes from libtool 2.4.2. :info:build libtool: You should recreate aclocal.m4 with macros from libtool 2.4 :info:build libtool: and run autoconf again. :info:build libtool: Version mismatch error. This is libtool 2.4, but the :info:build libtool: definition of this LT_INIT comes from libtool 2.4.2. :info:build libtool: You should recreate aclocal.m4 with macros from libtool 2.4 :info:build libtool: and run autoconf again. :info:build make[3]: *** [basedir.lo] Error 63 :info:build make[3]: *** [ccutil.lo] Error 63 :info:build libtool: Version mismatch error. This is libtool 2.4, but the :info:build libtool: definition of this LT_INIT comes from libtool 2.4.2. :info:build libtool: You should recreate aclocal.m4 with macros from libtool 2.4 :info:build libtool: and run autoconf again. :info:build make[3]: *** [bits16.lo] Error 63 :info:build libtool: Version mismatch error. This is libtool 2.4, but the :info:build libtool: definition of this LT_INIT comes from libtool 2.4.2. :info:build libtool: You should recreate aclocal.m4 with macros from libtool 2.4 :info:build libtool: and run autoconf again. :info:build libtool: Version mismatch error. This is libtool 2.4, but the :info:build libtool: definition of this LT_INIT comes from libtool 2.4.2. :info:build libtool: You should recreate aclocal.m4 with macros from libtool 2.4 :info:build libtool: and run autoconf again. :info:build make[3]: *** [elst.lo] Error 63 :info:build make[3]: *** [elst2.lo] Error 63 :info:build libtool: Version mismatch error. This is libtool 2.4, but the :info:build libtool: definition of this LT_INIT comes from libtool 2.4.2. :info:build libtool: You should recreate aclocal.m4 with macros from libtool 2.4 :info:build libtool: and run autoconf again. :info:build make[3]: *** [errcode.lo] Error 63 :info:build libtool: Version mismatch error. This is libtool 2.4, but the :info:build libtool: definition of this LT_INIT comes from libtool 2.4.2. :info:build libtool: You should recreate aclocal.m4 with macros from libtool 2.4 :info:build libtool: and run autoconf again. :info:build make[3]: *** [boxread.lo] Error 63 :info:build libtool: Version mismatch error. This is libtool 2.4, but the :info:build libtool: definition of this LT_INIT comes from libtool 2.4.2. :info:build libtool: You should recreate aclocal.m4 with macros from libtool 2.4 :info:build libtool: and run autoconf again. :info:build make[3]: *** [clst.lo] Error 63 :info:build make[3]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_tesseract/tesseract/work/tesseract-3.01/ccutil' :info:build make[2]: *** [all-recursive] Error 1 :info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_tesseract/tesseract/work/tesseract-3.01/ccutil' :info:build make[1]: *** [all-recursive] Error 1 :info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_tesseract/tesseract/work/tesseract-3.01' :info:build make: *** [all] Error 2 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_tesseract/tesseract/work/tesseract-3.01' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_tesseract/tesseract/work/tesseract-3.01" && /usr/bin/make -j9 -w all :info:build Exit code: 2 :error:build org.macports.build for port tesseract returned: command execution failed :debug:build Error code: CHILDSTATUS 48507 2 :debug:build Backtrace: command execution failed while executing "system -nice 0 $fullcmdstring" ("eval" body line 1) invoked from within "eval system $notty $nice \$fullcmdstring" invoked from within "command_exec build" (procedure "portbuild::build_main" line 8) invoked from within "$procedure $targetname" :info:build Warning: targets not executed for tesseract: org.macports.activate org.macports.build org.macports.destroot org.macports.install :notice:build Please see the log file for port tesseract for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_tesseract/tesseract/main.log
Attachments (1)
Change History (7)
comment:1 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ryandesign@… added |
---|---|
Description: | modified (diff) |
Owner: | changed from macports-tickets@… to emer@… |
Port: | tesseract added |
comment:2 Changed 12 years ago by markemer (Mark Anderson)
comment:3 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Summary: | tesserac not building due to incorrect version of libtool → tesseract not building due to incorrect version of libtool |
---|
Also builds fine for me. Please "sudo port clean tesseract", then try again, and attach the main.log file to this ticket if it fails again.
comment:4 follow-up: 5 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Daniel emailed me his log, which I have attached to this ticket. The relevant difference seems to be that in his log configure says:
:info:configure Running libtoolize :info:configure libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `config'. :info:configure libtoolize: copying file `config/ltmain.sh' :info:configure libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'. :info:configure libtoolize: copying file `m4/libtool.m4' :info:configure libtoolize: copying file `m4/ltoptions.m4' :info:configure libtoolize: copying file `m4/ltsugar.m4' :info:configure libtoolize: copying file `m4/ltversion.m4' :info:configure libtoolize: copying file `m4/lt~obsolete.m4'
whereas in my log configure says:
:info:configure Running libtoolize :info:configure ./autogen.sh: line 50: libtoolize: command not found :info:configure glibtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `config'. :info:configure glibtoolize: copying file `config/ltmain.sh' :info:configure glibtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'. :info:configure glibtoolize: copying file `m4/libtool.m4' :info:configure glibtoolize: copying file `m4/ltoptions.m4' :info:configure glibtoolize: copying file `m4/ltsugar.m4' :info:configure glibtoolize: copying file `m4/ltversion.m4' :info:configure glibtoolize: copying file `m4/lt~obsolete.m4' :info:configure ./autogen.sh: line 51: libtoolize: command not found
Basically, on my system, configure looked for and didn't find "libtoolize", and therefore looked for and found "glibtoolize" (provided by the libtool port). This is normal and how it should be working; there's not supposed to be a "libtoolize" on OS X. But on Daniel's system, configure found and therefore used "libtoolize". So the question for Daniel is: where is "libtoolize" on your system, why is it there, where did it come from, and what happens if you remove it?
comment:5 follow-up: 6 Changed 12 years ago by werner@…
I had the same problem and solved it by stripping my $PATH.
A newer version of "libtools" was requested by another lib, I forgot which one it was. I build and installed the newest libtool and that library build well. "libtool" installs itself in /usr/local/bin . "make" of tesseract build well after stripping the path ( was /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin ) by
export PATH=/usr/bin:/bin:/usr/sbin:/sbin ./autogen.sh make
Obviously nothing else in /usr/local/bin was required. Of course because of the tesseract - program is installed in /usr/local/bin you have to reset $PATH or use a new shell window before executing tesseract.
comment:6 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | werner@… added |
---|---|
Resolution: | → invalid |
Status: | new → closed |
Replying to ryandesign@…:
Basically, on my system, configure looked for and didn't find "libtoolize", and therefore looked for and found "glibtoolize" (provided by the libtool port). This is normal and how it should be working; there's not supposed to be a "libtoolize" on OS X. But on Daniel's system, configure found and therefore used "libtoolize". So the question for Daniel is: where is "libtoolize" on your system, why is it there, where did it come from, and what happens if you remove it?
Daniel sent me email saying removing libtoolize worked:
From: Daniel Bertrand
Subject: Re: [MacPorts] #35700: tesseract not building due to incorrect version of libtool
Date: August 17, 2012 21:20:22 CDT
that worked.
removed libtoolize...
sudo port install tesseract ---> Computing dependencies for tesseract ---> Fetching archive for tesseract ---> Attempting to fetch tesseract-3.01_1.darwin_12.x86_64.tbz2 from http://packages.macports.org/tesseract ---> Attempting to fetch tesseract-3.01_1.darwin_12.x86_64.tbz2 from http://macports.packages.ionic.de/tesseract ---> Fetching distfiles for tesseract ---> Verifying checksum(s) for tesseract ---> Extracting tesseract ---> Applying patches to tesseract ---> Configuring tesseract ---> Building tesseract ---> Staging tesseract into destroot ---> Installing tesseract @3.01_1 ---> Activating tesseract @3.01_1 ---> Cleaning tesseract ---> Updating database of binaries: 100.0% ---> Scanning binaries for linking errors: 100.0% ---> No broken files found.
You are awesome, thank you for your help.
Replying to werner@…:
[snip] I build and installed the newest libtool and that library build well. "libtool" installs itself in /usr/local/bin . [snip]
Installing software in /usr/local will cause problems for MacPorts, so we don't support doing that. Please ensure /usr/local is empty if you want to use MacPorts, or at least, if you want help when things go wrong.
I can't reproduce this. Can anyone else?