Other libraries (including OpenFST) also have problems involving PIC and 64bit machines. I'm not sure what the underlying problem is or what the right solution is. I've seen it on some installations of Linux and not others--even nominally the same Ubuntu release.
This may be a bug in the compiler/linker on some platforms, or it may mean that there is something wrong with the autoconf files. Anybody who has an idea of what the cause is--please let us know. The workaround seems to be just what you did: follow the error messages and add -fPIC to the compilation flags. Tom On Sat, Nov 29, 2008 at 02:53, shao.d <[EMAIL PROTECTED]> wrote: > > > On Nov 28, 10:35 am, Andrew <[EMAIL PROTECTED]> wrote: > > > OK, i seem to have compiled ocropus. > > High five! :-) > > > > > deleting the old /usr/local/lib/libiulib.a did not help. (I deleted, > > then recompiled iulib, making sure it was the latest SVN, with the > > patching and autoreconf-ing). What DID help was to add the "-fPIC" > > flag to the iulib ./configure. > > From my reading of > http://www.gentoo.org/proj/en/base/amd64/howtos/index.xml?part=1&chap=3 > it appears that one of the libraries that iulib is built against is a > static library. Looking at the configure output and the compilation > output would probably indicate which one. > > The gentoo link above seems to indicate that what you did, feeding the > -fPIC flag, is how to force linking to a static library. > > > And I did not need to give ocropus ./configure any options at all. > > > > (my iulib configure command was: > > > > ./configure CFLAGS="-fPIC -DPIC" CPPFLAGS="-fPIC -DPIC" > > CXXFLAGS="-fPIC -DPIC" > > I wouldn't sweat the shared versus static library distinction > considering the voyage you have completed just to get ocropus built. > The decision of whether to switch to using libtool for building > libraries is one that the developers of leptonlib, OpenFst, tesseract, > iulib, and ocropus all might have to make together to get a unified > autotooled software stack that can be easily distributed through > package managers on all platforms. I would argue that shared > libraries make updating easier, important for software that deals with > image manipulation formats because these appear to sometimes need > security updates to fix problems like buffer overflows, but obviously > this decision is not in our hands. > > Anyway, congratulations, and thanks for sharing your tips for > compilations success. :-) > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "ocropus" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/ocropus?hl=en -~----------~----~----~----~------~----~------~--~---
