#35700: tesseract not building due to incorrect version of libtool -----------------------------------------+---------------------------------- Reporter: danieljamesbertrand@… | Owner: emer@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: invalid | Keywords: Port: tesseract | -----------------------------------------+---------------------------------- Changes (by ryandesign@…): * cc: werner@… (added) * status: new => closed * resolution: => invalid Comment: Replying to [comment:4 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 [[br]] Subject: Re: [MacPorts] #35700: tesseract not building due to incorrect version of libtool [[br]] Date: August 17, 2012 21:20:22 CDT [[br]] [[br]] that worked. [[br]] [[br]] removed libtoolize... [[br]]
{{{ 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 [comment:5 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. -- Ticket URL: <https://trac.macports.org/ticket/35700#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS