There is no "standard" time a compile could/should run... it depends on the package to be built... some are in seconds others in hours and there are some that take days.

My record... it was not really a slackbuild... it was not that standardized yet at that time afaik... it was on my i486 100MHz (what a beast that was!):
- it took days to compile a 2.x kernel (and then to find out you missed a flag here or there and it wouldn't boot...)
- It took even more days to compile X
- and dare I guess how long it took to compile enlightenment?

Let's say the above "upgrades" took more than a month in total, due to the amount of (re)compile time

Oh; and webkitgtk3 is one of those long compiles... easily takes a few hours... as long as you see activity, don't worry... it'll come... eventually

enlightenment doesn't really take that much time to compile

The last time I compiled webkitgtk (November of last year) I used -j7 and it compiled successfully. Just for giggles I decided compile it again. It is currently in the make stage and using all 6 of my CPUs. I started the SlackBuild @ 17:46 my time.

LoL, there is actually data about everything

Finished 18:34, 48 minutes.

Attached Thumbnails

 

OpenJDK can be up there in time frames too.

There are plenty of opinions about whether you lose performance running 32 bit code on a 64 bit processor, but not much actual data. So, here is a comparison of build times on the same box between Slackware 14.2RC1 x86_84 and i586. You can see that the i586 builds are consistently slower, sometimes quite significantly, with only a couple of exceptions.

https://gist.github.com/idlemoor/90d...3a831da3254ca0

This isn't yet the complete set of 5600 packages (it's only been running since yesterday) but I'll update it when it finishes.

In other news, a clever observer would be able to use the other gist I posted to make a list of packages that currently fail to build

1 members found this post helpful.

That's been a bug in make and it has been fixed a long time ago on -current. Jun 1, 2014 to be exact:

1 members found this post helpful.

show-off

The icecat browser took many hours. I took one look at it and yawned. Just another Firefox clone.
This was on a 32 bit netbook

Build it wenesday as dependency for luakit, quite long, yes. Ffmpeg was too if I recall correctly.

it did; back in ... I think it was around 1990 :-) But then; I think it might also have been kde... was my days of exploring desktop environments / window managers.

ffmpeg wasn't so long... in itself, but that list of (possible) dependencies...

Reminds me of that one time I had to compile a haskell program. That wasn't so bad; but having to install a gazillion subpackages that are requirements of requirements of requirements (ended up installing 200 deps...; how I remained sane... or I never was, and only think I am)

Ah, got it:-
Thanks-