[MacPorts] #35700: tesseract not building due to incorrect version of libtool
MacPorts
noreply at macports.org
Fri Aug 17 19:12:48 PDT 2012
#35700: tesseract not building due to incorrect version of libtool
----------------------------------------+-----------------------------------
Reporter: danieljamesbertrand@… | Owner: emer@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.1.2
Keywords: | Port: tesseract
----------------------------------------+-----------------------------------
Comment(by ryandesign@…):
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?
--
Ticket URL: <https://trac.macports.org/ticket/35700#comment:4>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list