Bug#774164: libocrad-dev: libocrad.a contains non-reallocatable code
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 unrelated, and the error message is misleading. What is needed to fix these test results is to have the library compiled with PIE, and the rebuild triggered by my 0.25-2 QA upload will do the job (even a binNMU would have been sufficient). After that the library is again usable for linking into binaries. This bug here is about compiling the static library with -fPIC for making it suitable for inclusion in shared libraries. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: Re: Bug#774164: libocrad-dev: libocrad.a contains non-reallocatable code
Processing control commands: > severity -1 normal Bug #774164 [libocrad-dev] libocrad-dev: libocrad.a contains non-reallocatable code Severity set to 'normal' from 'grave' -- 774164: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774164 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#774164: libocrad-dev: libocrad.a contains non-reallocatable code
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 for adding me to the recipient list, but I don't have the > motivation to help here. > > Added Jakub Wilk to copy, IIRC he made the package. I see from the build log [1] that the build policy for .a had changed... I think that is for good. Relocatable code makes object a bit bigger, but on current systems that does not matter at all. Briefly: 1. One solution would be to make .a code reallocatable, so that .so library that refers libocrad.a can compile. 2. Another solution is to provide libocrad.so within libocrad package. [1] https://ci.debian.net/data/packages/unstable/amd64/o/ocrad/20161215_073147.autopkgtest.log.gz -- With best regards, Dmitry
Bug#774164: libocrad-dev: libocrad.a contains non-reallocatable code
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 motivation to help here. Added Jakub Wilk to copy, IIRC he made the package. Thanks. -- Mit freundlichen Grüßen Alexander Alemayhu
Processed: Re: Bug#774164: libocrad-dev: libocrad.a contains non-reallocatable code
Processing control commands: > severity -1 grave Bug #774164 [libocrad-dev] libocrad-dev: libocrad.a contains non-reallocatable code Severity set to 'grave' from 'normal' -- 774164: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774164 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
