Control: severity -1 normal
On Thu, Dec 15, 2016 at 09:42:08PM +0100, Petter Reinholdtsen wrote:
> Control: severity -1 grave
>...
> If I understand the test results from
> https://ci.debian.net/packages/o/ocrad/unstable/amd64/ > correct, the
> library is no longer usable.
>...
That's mostly
On 2016-12-16 10:16, Alexander Alemayhu wrote:
> On Thu, Dec 15, 2016 at 09:42:08PM +0100, Petter Reinholdtsen wrote:
>>
>> Personally I use tesseract these days for my OCR work, and do not need ocrad.
>
> I have unfortunately stopped using ocrad in favour of proprietary
> solutions.
>
> Thanks
On Thu, Dec 15, 2016 at 09:42:08PM +0100, Petter Reinholdtsen wrote:
>
> Personally I use tesseract these days for my OCR work, and do not need ocrad.
I have unfortunately stopped using ocrad in favour of proprietary
solutions.
Thanks for adding me to the recipient list, but I don't have the
Control: severity -1 grave
[Alexander Alemayhu 2014-12-30]
> will look closer at this later today.
This was the last words from the previous maintainer, and do not apply today.
If I understand the test results from
https://ci.debian.net/packages/o/ocrad/unstable/amd64/ > correct, the
library
Package: libocrad-dev
Version: 0.24-1
Hi,
It turned out that the -dev package contains the code in libocrad.a
which is not compiled with -fPIC. These object files can be used when
linking the executable, but not when linking the dynamic library (my case).
As far as I can see libocrad.a is used
On Mon, Dec 29, 2014 at 08:24:52PM +0100, Dmitry Katsubo wrote:
Hi,
Hei Dmitry,
It turned out that the -dev package contains the code in libocrad.a
which is not compiled with -fPIC. These object files can be used when
linking the executable, but not when linking the dynamic library (my
6 matches
Mail list logo
