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.
Make install for python-3 does not create a /usr/bin/python symlink or a /usr/bin/python-config symlink.
I think it's better to leave things as they are and assume that /usr/bin/python will always point to python2. That is, until python2 goes away, at which point I don't think there should be a /usr/bin/python symlink at all.
Drop python2 for good in the next release, pretty please.
This would be the first Slackware yet to release a "dead" peace of software, at least since the brand new fashion to "end of life" software, as if it has expiry date on it.
But i think the smart way is to move it to /pasture/ for the time. Innit funny and nice how our Slackware has convenient and readily available solutions for whatever comes along?
this will actually need a little bit of massaging as some extensions have been deprecated or build options have changed, apart for a newly introduced dependency, oniguruma: I've built a local package for testing using this script (and took oniguruma from SBo).
In my configuration (compilation from sources) I have two changes:
1. oniguruma package is really needed, it can be added to Slackware.
2. --enable-zip -> --with-zip
Last edited by teoberi; 11-29-2019 at 04:13 AM.
Reason: post completion
In my configuration (compilation from sources) I have two changes:
1. oniguruma package is really needed, it can be added to Slackware.
2. --enable-zip -> --with-zip
mainly there's also "--with-gd=shared" that becomes "--enable-gd=shared --with-external-gd" (or it won't build the gd.so extension) and the line "extension=wddx" that must be removed from the php.ini-development.diff.gz because the wddx extension has been moved to PECL.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.