LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   What's The Longest Amount of Time A SlackBuild Has Been Running? (https://www.linuxquestions.org/questions/slackware-14/whats-the-longest-amount-of-time-a-slackbuild-has-been-running-4175576947/)

Ztcoracat 04-07-2016 04:08 PM

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?

OldHolborn 04-07-2016 04:17 PM

Webkitgtk :)

On a Pentium P133, approx 7 days

I was build Midori

bassmadrigal 04-07-2016 04:23 PM

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.

http://packages.slackonly.com/pub/pa...ies/webkitgtk/

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.

55020 04-07-2016 04:41 PM

Build times in seconds for 14.2 master running on a 4 x 3.5GHz box:
https://gist.github.com/idlemoor/57f...4964dca76d4842

(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.)

Didier Spaier 04-07-2016 06:26 PM

Quote:

Originally Posted by OldHolborn (Post 5527815)
Webkitgtk :)

On a Pentium P133, approx 7 days

I was build Midori

I would get both from Salix :)

astrogeek 04-07-2016 06:38 PM

Hi Ztcoracat!

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! ;)

Ztcoracat 04-07-2016 06:58 PM

Quote:

Originally Posted by OldHolborn (Post 5527815)
Webkitgtk :)

On a Pentium P133, approx 7 days

I was build Midori

7 Days; my word that's an awfully long time. Are you cereal?
LOL

Ztcoracat 04-07-2016 07:00 PM

Quote:

Originally Posted by astrogeek (Post 5527871)
Hi Ztcoracat!

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! ;)

Yup, a virtue indeed.

Ztcoracat 04-07-2016 07:02 PM

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.

Skaendo 04-07-2016 07:59 PM

Quote:

Originally Posted by Ztcoracat (Post 5527806)
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.

Ztcoracat 04-07-2016 08:14 PM

Quote:

Originally Posted by Skaendo (Post 5527911)
I just compiled webkitgtk3 not too long ago and it took just about 6 hours on my Core2Duo @ 2Ghz & 4 GB RAM.

Thanks for trying it.

Any clue why some SlackBuild scripts take longer than others?

D1ver 04-07-2016 08:33 PM

Quote:

Originally Posted by Ztcoracat (Post 5527917)
Thanks for trying it.

Any clue why some SlackBuild scripts take longer than others?

The more code you have to compile the longer it's going to take. WebkitGtk is a massive codebase :)

Ztcoracat 04-07-2016 08:38 PM

Quote:

Originally Posted by D1ver (Post 5527929)
The more code you have to compile the longer it's going to take. WebkitGtk is a massive codebase :)

I just found out webkitgtk builds the gtk interface.
That explains why it took so long plus all of the code to compile.

I bet it wasn't a walk in the park to put that script together.

willysr 04-07-2016 09:05 PM

sage, xulrunner, webkitgtk{3}, and webkit2gtk are the ones that took some time to build.

TobiSGD 04-08-2016 12:31 AM

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.


All times are GMT -5. The time now is 11:32 PM.