[Slackbuilds-users] qemu build issue

Matteo Bernardini matteo.bernardini at gmail.com
Mon Mar 21 12:54:52 UTC 2022

well, to be fair that shouldn't actually be a problem in a Slackware stable
setup because libraries' versions should be the same...
that should only happens when you are using current or upgrading between
Slackware versions (but in that case many other things could happen).


Il giorno lun 21 mar 2022 alle ore 13:48 Tim Dickson via SlackBuilds-users <
slackbuilds-users at slackbuilds.org> ha scritto:

> thanks Matteo, that did the trick. It looks like part of the build process
> uses already created binaries to process files, and when older binaries are
> already in the path they are used instead, giving the error.
> It may be worth adding a comment to remove existing version of qemu before
> installing a newer one into the README.
> regards, Tim
> On 20/03/2022 18:31, Matteo Bernardini wrote:
> have you tried removing the already installed qemu package first?
> Il giorno dom 20 mar 2022 alle ore 19:29 Tim Dickson via SlackBuilds-users
> <slackbuilds-users at slackbuilds.org> ha scritto:
>> I am getting the following error when attempting to create qemu package.
>> /usr/bin/qemu-keymap: error while loading shared libraries:
>> libjemalloc.so.1: cannot open shared object file: No such file or
>> directory
>> /usr/lib64/libjemalloc.so links to usr/lib64/libjemalloc.so.2 so there
>> is a libjemalloc installed (part of slackware 15.0).
>> It seems that the build script is looking for the wrong version of the
>> lib. Ideally it would try libjemalloc.so and thus pick up whichever
>> version was installed.
>> Is there a quick fix. (if it involves a sim-link would that have to be
>> done on target computers as well?)
>> regards, Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220321/46523b99/attachment.htm>

More information about the SlackBuilds-users mailing list