[SOLVED] What's The Longest Amount of Time A SlackBuild Has Been Running?
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.
What's The Longest Amount of Time A SlackBuild Has Been Running?
I started a SlackBuild script (webkitgtk3) this afternoon around 1 p.m......It's now a few minutes after 5 p.m. and it's still running.
I've never seen a script run for this long before:-
Is this the norm?
What slackbuild script have you ran and how long did it take?
Depending on your system, at least several hours (it probably take around a day on mine since my system is 8+ years old). I'd probably grab the pre-compiled binary provided by slackonly. See another concerned user about this on the SBo mailing list.
Libreoffice is also a really long compile... If I really feel the need to compile it myself, I'll usually do it right before bed so I don't have to wait for it to finish. That's what I did when I recompiled X and qt.
(When you build stuff with slackrepo it uses a database of these figures to give you the estimated time when the build will finish, and then it records your actual build time to give an improved estimate next time ... other tools are welcome to steal the idea, and indeed the build time data.)
I have not built webkitgtk3, but for me the record was xulrunner. Last build that succeeded on my old single core 32 bit machine ran many hours. It now requires such an obscene amount of RAM/swap to build that I have put it in my no-build-zone.
So some of them can run for a long time... patience is a virtue!
I have not built webkitgtk3, but for me the record was xulrunner. Last build that succeeded on my old single core 32 bit machine ran many hours. It now requires such an obscene amount of RAM/swap to build that I have put it in my no-build-zone.
So some of them can run for a long time... patience is a virtue!
Thanks for the feedback guys. The script finally stopped and gave me the x86_64-1_SBO I needed.
It took about 5 hours on my desktop pc that's about 5 years old.
I started a SlackBuild script (webkitgtk3) this afternoon around 1 p.m......It's now a few minutes after 5 p.m. and it's still running.
I've never seen a script run for this long before:-
Is this the norm?
What slackbuild script have you ran and how long did it take?
I just compiled webkitgtk3 not too long ago and it took just about 6 hours on my Core2Duo @ 2Ghz & 4 GB RAM.
What's The Longest Amount of Time A SlackBuild Has Been Running?
IIRC, the problem with webkitgtk is that it has to be compiled with -j1, so that it (unlike most other software) can not take advantage of multicore CPUs.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
