[Slackbuilds-users] Direct linking so files instead of linked so files?

Willy Sudiarto Raharjo willysr at slackbuilds.org
Sun Aug 14 02:09:38 UTC 2016

> Ok, first off this is a rhetorical question. I'm away from my home computer
> and will have to research it from there.  However, however, if anyone has
> any words of wisdom about this, by no means does this question need to be
> answerless. (My brain works in horrible ways, and this happens to work for
> me, so meh, make of it what you will, HAH).
> Anyhoo!  While trying to run an app I maintain (equalx) I realized that the
> latest upgrade to 14.2 (which was current back those many moons ago) kind
> of broke because of the symlink to libpoppler.  libpoppler.so.58 was the
> originally linked library, but now I have libpoppler.so.62.  Sooo, in the
> offchance that certain particular routines in a library for a piece of
> software wouldn't need an upgrade, what could be searched in the Makefile
> to force it to compile using the non-linked library in order to diff and
> patch?

normally a simple rebuilt will fix the issue

Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160814/50261bfb/attachment.asc>

More information about the SlackBuilds-users mailing list