[Gambas-bugtracker] Bug #1560: gb.pdf fails to load every time libpoppler is updated

[Tony Morehen]

When you recompile Gambas, it automatically links to the current version 
of libpoppler (when you autoreconf all), so you run the risk of 
incompatible apis any way.

One solution would be to have Gambas link to /usr/lib/libpoppler.so.

On my system, there are 3 versions of libpoppler:

/usr/lib/libpoppler.so   symlink to...
/usr/lib/libpoppler.so.86  symlink to...
/usr/lib/libpoppler.so.86.0.0  the actual file


On 2019-04-04 12:50 p.m., bugtracker at gambaswiki.org wrote:
> http://gambaswiki.org/bugtracker/edit?object=BUG.1560&from=L21haW4-
> 
> Comment #2 by Tobias BOEGE:
> 
> When you link an object to a shared library, the .so's path is recorded in the object:
> 
>    $ readelf -d /usr/lib/gambas3/gb.pdf.so | grep poppler
>    0x0000000000000001 (NEEDED)             Shared library: [libpoppler.so.85]
>    $ ldd /usr/lib/gambas3/gb.pdf.so | grep poppler
>    libpoppler.so.85 => /usr/lib/libpoppler.so.85 (0x00007fde27205000)
> 
> Otherwise you'd update poppler, it changes its version number (indicating a breaking change
> most likely) and risk calling into an incompatible API/ABI.
> 
> If you update your libraries, you have to recompile Gambas. Isn't that normal?
> 
>