Creating python + pygame binaries on Slackware 13.37 problem.
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Creating python + pygame binaries on Slackware 13.37 problem.
Hi All,
I was a happy Slackware user for past 10 years. Until yesterday that is.
I have created a small game with python and pygame which works fine from sources.
Problem starts when i wanted to create a binary. Using cx_freeze or pyinstaller i got no errors while compiling and standalone build. Works ok on slackware.
I got users which reported problems on Debian and possibly others:
File "/usr/lib/python2.6/site-packages/cx_Freeze/initscripts/Console.py", line 27, in <module>
File "DarkGates.py", line 30, in <module>
File "DarkGates.py", line 16, in main
pygame.error: File is not a Windows BMP file"
This is due libpng is not loaded properly (got segfaults as well when build with pyinstaller), which is bundled with binary.
Now, i did a binary form same source under Linux Mint, and binary worked fine on Debian nad Fedora (different enough ?). It works on Slackware bo has some minor problems.
Kind of pulling may hair out why build on Slackware not working elsewhere. All testing done under 32-bit env.
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,511
Rep:
The default libpng ( libpng.so ) is version 1.4.5 in Slackware (13.37)
and thus incompatible with Debian, Ubuntu, Fedora, CentOS, etc.,
which all use version 1.2.4x.
( Slackware has a "libpng12.so.0.44.0" included too.)
A workaround could be : cd /usr/lib/ && mv libpng.so libpng.so-back
&& ln -s libpng12.so.0.44.0 libpng.so
..... Then all build of software will use the compatible libpng12.so.0.44.0
( At least compatible with the latest versions of Debian, Ubuntu, Fedora.
but probably not with all older versions : Ubuntu 10.10 libpng 1.2.44,
Debian Squeeze libpng 1.2.44, Fedora 14 libpng 1.2.44 or later.)
Thanks knudfl this will explain a lot but one thing is still unclear. So why Slackware is not happy with binary package which has been build with older version of libpng ? Newer libpng in Slackware should have no problem, right ? yet it have.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.