Hello, Unregistered. This is an update to the transition of the forums to Ubuntu Discourse . As previously notified, this site is no longer accepting new support threads pending its closure . Any such threads will be closed. Anyone needing support for Ubuntu or the official flavours should seek help at Ubuntu Discourse (see below). Forum members will still be able to post to open threads until this site becomes read-only on or about January 9th 2025. This is so that those who had started help threads just before the transition are not left without support. Please do not post requests for help to others' threads during this period. Thread hijack posts, "me-too's" and similar will be removed from public view. If you have not already done so, you can log into Ubuntu Discourse using the same Ubuntu One SSO account that is used for logging into ubuntuforums. If you are new to Ubuntu Discourse please read this page first. Please be aware that after your first login you will not be able to post any topic in Ubuntu Discourse until you have spent some time exploring the site and reading some posts. The Support and Help section will be the first to be open to you for posting. Thereafter, as you gain trust, you will find other sections of Discourse open to you. If you are experiencing any difficulty using Discourse and are unable to post there for help, have a look at this thread which will be monitored by the transition team, and where you may ask for help if the answer is not there already. I've just downloaded and installed the purebasic program language (from www.purebasic.com - the paid-for version) into my 16.04 system.
But on trying to launch purebasic in Terminal, I get this error:

purebasic: /lib/x86_64-linux-gnu/libz.so.1: version `ZLIB_1.2.9' not found (required by purebasic)

In that folder, owned by root, there is libz.so.1 and libz.1.2.8 and the first is just a link to the second. There is no libz.1.2.9
How should I fix this?
In two or three places (incl a thread on this forum) there is a suggestion along the lines of
move (surely this should be copy?) libz.so.1 to the program folder - in this case, .../purebasic/compilers (which is in the $PATH) - and then
ln -sf libz.so.1
but there must be more to it than this, since libz.1.2.9 does not exist anywhere on my system. I think messing with the libz on root might mess up my system, and I am not expert enough to deal with that. Unfortunately I do not have access to 18.04.
I do have access to a separate 20.04 machine. If I copy libz_1.2.11 from there on to my 16.04 box, would it be backwards compatible? If so, can I ring-fence it to the purebasic environment so that it does not trip anything else up?
If so, how?
Would putting it into the purebasic/compilers folder with an accompanying lib.so.1 link do the trick? Most likely libz_1.2.[9|11] links to some other shared object which does not exist on 16.04. And even if you get the zlib sorted, the downloaded software is probably linked to other SO's not available anywhere else than 18.04. I'm not familiar with purebasic, but if you've bought a license to the software, you should contact the vendor and ask their support what to do. EDIT:
I've raised it with purebasic support but I don't expect a reply for a few days (it is currently the weekend, and in any case the Covid pandemic may have affected working hours in France/Germany)
There is a thread on the purebasic forum which raised this issue quite a while ago, but it looks as if this was a "we are working on this" matter which has not yet been resolved. I can't see it being a high priority because later versions of Ubuntu have a later version of libz (1.2.11 is currently the latest and is the one recommended on the software website) so for most new users the problem will not be present. I imagine that purebasic 5.72 requesting 1.2.9 does not mean it won't work with 1.2.11!
My workaround pending advice from purebasic is to download purebasic 5.70, which does fire up its IDE - although (being well past bedtime) I haven't tried writing even "Hello World" yet!
Not marked as SOLVED because this is a workaround, not really a solution. vBulletin ©2000 - 2024, Jelsoft Enterprises Ltd. Ubuntu Logo, Ubuntu and Canonical © Canonical Ltd. Tango Icons © Tango Desktop Project. User contributions on this site are licensed under the Creative Commons Attribution Share Alike 4.0 International License . For details and our forum data attribution, retention and privacy policy, see here