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.
I'm still working away at this, slowly. May have something to show
pretty soon, if I can just get some consistency in the builds. Everytime
I fix one thing another goes bonkers.
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint...
Posts: 1,564
Rep:
Well I finally got everything working (It was just before the big python3 update):
-nfs-utils: small patch
-herqq: new patch
-calligra: build it at the very end
-clisp: build a new version (used 'hg clone http://hg.code.sf.net/p/clisp/clisp clisp-2.49')
-rust: still locked at 1.19 version
I was looking over the KDE build in your scripts and noticed in
the functions build_post_kde1 and 2, you rebuild several of the
KDE programs, but never re-install them. Is this correct?
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint...
Posts: 1,564
Rep:
You're right, it's a mistake.
Thanks for the warning, I'll correct it when I find time to do it.
There has been a lot of changes in slackware-current since september.
Actually it's installed by the KDE.SlackBuild. I realized this as soon
as I woke up this morning. My question was inspired by partying and
lack of sleep. Sorry.
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint...
Posts: 1,564
Rep:
question to Worsel: have-you a version of sfsinit script working for x86_64, there is something wrong with adjust_x86_64 in mine, it segfaults after that step. I can go on and build manually, but not with sfsbuild script?
question to Worsel: have-you a version of sfsinit script working for x86_64, there is something wrong with adjust_x86_64 in mine, it segfaults after that step. I can go on and build manually, but not with sfsbuild script?
Don't know, as I am assuming you are building -current. I'm still working on -14.2 and using what is basically your sfsinit script from 20170109. I suppose i should
just give up on it and start working on -current. Can't get kde to completely build. amarok, kdeartwork, kdesdk-kioslaves, kgamma, kuser, and kdev-python refuse to build.
Post a copy of your sfsinit and I'll see if I can spot the problem.
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint...
Posts: 1,564
Rep:
adjust to the latest version available at the time you rsync your local slackware repository. No less, no more! It's for current version, so it moves nearly every day...
This happens from the command line or from a script.
I haven't traced this down yet. Google returns only a few old (1997 or so) threads on this.
None of them seem particulary helpful. Don't know if this is related to the first problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.