Re: [Slackbuilds-users] pytesseract
On Sun, Nov 10, 2019 at 03:38:00PM -0500, Judah Milgram wrote: > > > Thanks for upgrading the slackbuild to tesseract 4! > > Related thought: sure would be nice to have pytesseract. Is it already part > of an existing slackbuild? > > If not, I'd be happy to take a stab at it. It doesn't look like pytesseract is part of an existing slackbuild. So I'm sure you could feel free to submit to slackbuilds.org. However, it should be noted that pytesseract is also installable from pip. I'm not sure what (if anything) the SBo policy is on this, but it would seem to me that unless a perl or python package is needed as a dependency for something else, users might be best off installing those packages from CPAN or pip, so as to avoid duplication of effort. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] pytesseract
Thanks for upgrading the slackbuild to tesseract 4! Related thought: sure would be nice to have pytesseract. Is it already part of an existing slackbuild? If not, I'd be happy to take a stab at it. On 11/9/19 1:57 PM, Logan Rathbone wrote: On Sat, Nov 09, 2019 at 09:22:19AM -0500, John Yost wrote: getting following error: libtool: link: ranlib .libs/libtesseract_api.a libtool: link: ( cd ".libs" && rm -f "libtesseract_api.la" && ln -s "../libtesseract_api.la" "libtesseract_api.la" ) /bin/sh ../../libtool --tag=CXX --mode=link g++ -g -O2 -std=c++17 -llept -larchive -version-info 4:1-o libtesseract.la -rpath /usr/lib64 libtesseract_api.la ../ccmain/libtesseract_main.la ../textord/libtesseract_textord.la ../wordrec/libtesseract_wordrec.la ../classify/libtesseract_classify.la ../dict/libtesseract_dict.la ../arch/libtesseract_arch.la ../arch/libtesseract_native.la ../lstm/libtesseract_lstm.la ../ccstruct/libtesseract_ccstruct.la ../cutil/libtesseract_cutil.la ../viewer/libtesseract_viewer.la ../ccutil/libtesseract_ccutil.la ../opencl/libtesseract_opencl.la ../arch/libtesseract_avx.la ../arch/libtesseract_avx2.la ../arch/libtesseract_sse.la -lpthread /usr/bin/grep: /usr/lib64/liblzma.la: No such file or directory /usr/bin/sed: can't read /usr/lib64/liblzma.la: No such file or directory libtool: error: '/usr/lib64/liblzma.la' is not a valid libtool archive Makefile:536: recipe for target 'libtesseract.la' failed make[2]: *** [libtesseract.la] Error 1 make[2]: Leaving directory '/tmp/SBo/tesseract-4.1.0/src/api' Makefile:498: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/tmp/SBo/tesseract-4.1.0' Makefile:407: recipe for target 'all' failed make: *** [all] Error 2 any help is appreciated Works for me under -current and 14.2 (clean buildroot). If liblzma.la is not present on your system (it should be there on a clean 14.2 system) I'm assuming you're on -current. Sounds like you may have a broken chain of libtool archives (.la files). See the Slackware Current ChangeLog entry from April 19, 2018. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/ -- Judah Milgram milg...@cgpp.com 301-257-7069 ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] libc++-3.8.6 on slackware current xlocale.h not found.
Tankyou Dave, thanyou Matteo. @Dave I am trying to get https://github.com/codilime/veles running on my system. It needs so much stuff, I decided it might be easieer from slackware current. Dont worry about my personal trouble with libc++. 14.2 is working fine. @Matteo I probably built more stuff than I need but veles asks for a lot. qt-creator-llvm and Python/Sphings I am not sure if I really need them. That is how I got into libc++. If I really get veles running, I'll try to make a propper slackbuild. Update veles successfully built. It is more complicated than I thought but it looks beautiful. Cheers Peter On Sun, 10 Nov 2019 00:23:36 + Dave Woodfall wrote: On Sat 9 Nov 2019 23:52, Peter Dambier put forth the proposition: > Hi, I am Peter and I am new to this list. > > Building libc++ aborted with an "xlocale.h" not found error. > > Digging into the subject I found this xlocale.h actually is > a subset of locale.h and should never have escaped > into the wild - so now is the time to remove it. > > As it is not needed, it might actually be empty, why not > > touch /usr/include/xlocale.h > > Package libc++-3.8.6-i586-1_SBo.tgz build without any > more trouble. > > Of course this is not the right way to do it. But it may > save somebodys day and you can always delete > that xlocale.h immediately after building. > > Beware locate finds lots of xlocale.h: > > /usr/include/c++/v1/support/fuchsia/xlocale.h > /usr/include/c++/v1/support/ibm/xlocale.h > /usr/include/c++/v1/support/musl/xlocale.h > /usr/include/c++/v1/support/newlib/xlocale.h > /usr/include/c++/v1/support/solaris/xlocale.h > /usr/include/wx-3.0/wx/xlocale.h > > but this one used to belong to glibc and lived in > /usr/include. Hi Peter, I have xlocale.h in glibc-2.23 on 14.2. grep xlocale.h /var/log/packages/* /var/log/packages/glibc-2.23-x86_64-4_slack14.2:usr/include/xlocale.h Do you not have this? -Dave -- Peter and Karin Dambier Adalbert-Stifter-Strasse 17 D-69509 Moerlenbach +49(6209)280-3030 (VoIP: GGEW) +49(6252)750-308 (VoIP: sipgate.de) mail: pe...@peter-dambier.de ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
