point noted, and thanks. qemu was my first slackbuild to be built for 15.0 to get my dev vm's up to date so I can get on with the rest, including the ones i look after.
regards, Tim

On 21/03/2022 13:05, Dave Woodfall wrote:
On 21/03/22 13:54,
Matteo Bernardini <matteo.bernard...@gmail.com> put forth the proposition:
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).
Matteo
I've just put a small note at the bottom of the README, that if there
are any problems with missing or wrong versioned libraries to try
uninstalling older versions first.

Dave

Il giorno lun 21 mar 2022 alle ore 13:48 Tim Dickson via SlackBuilds-users <
slackbuilds-users@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@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


--
Dave
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



--
This email has been checked for viruses by AVG.
https://www.avg.com

_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Reply via email to