How much time does it take to compile glibc,gcc,kernel?

Message

colag · Post by **colag** » Thu Mar 06, 2014 6:38 am

Hi

How much does it take to compile glibc,gcc and kernel on your system?
For me, kernel takes around 30 minutes, gcc takes around 20 minutes and glibc takes around 25 minutes.
Please mention your pc hardware information.

Thanks.

fturco · Post by **fturco** » Thu Mar 06, 2014 10:10 am

On my system gcc requires 40-42 minutes and glibc requires 21-22 minutes.

Code: Select all

cat /proc/cpuinfo | grep "model name"
model name	: Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz
model name	: Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz

aCOSwt · Post by **aCOSwt** » Thu Mar 06, 2014 11:11 am

With same proc as fturco, glibc needs 15 to 16 minutes on my system.

(while watching mplayer...

)
But... gcc needs *a lot more* : that is 1 hour and 15 minutes...

(running single user...

)
OK... this is mainly because

Code: Select all

acoswt@PrimaPratica /etc/portage $ cat /etc/portage/env/sys-devel/gcc
GCC_MAKE_TARGET="profiledbootstrap"

I do recommend it (unless you frequently build gcc of course) it is really worth it.

BTW... you can see that comparing times for building something is just meaningless if you do not state precisely what you build (options) and how you build it.

Anon-E-moose · Post by **Anon-E-moose** » Thu Mar 06, 2014 2:15 pm

I usually do things like building gcc and glibc from console, pre starting X.

The last times I have were for an amd x6 1065 overclocked to 3.6 running 5 of six cores for build (1 reserved for me

)

sys-libs/glibc-2.15-r3 merge time: 11 minutes and 2 seconds.

sys-devel/gcc-4.7.3-r1 merge time: 18 minutes and 36 seconds.

I've since upgraded the cpu and have it overclocked to 4 ghz, but don't have timings yet.

Don't keep timings on the kernel, but it's nowhere near 30 min.

rudregues · Post by **rudregues** » Fri Mar 07, 2014 11:56 pm

kernel less than 5 minutes (I use seeds), the others:

Code: Select all

localhost rodrigo # genlop -t sys-libs/glibc sys-devel/gcc
 * sys-libs/glibc

     Wed Jan 15 23:04:37 2014 >>> sys-libs/glibc-2.17
       merge time: 57 minutes and 21 seconds.

 * sys-devel/gcc

     Tue Jan 28 00:29:52 2014 >>> sys-devel/gcc-4.7.3-r1
       merge time: 2 hours, 19 minutes and 35 seconds.

CPU: AMD E-350

steveL · Post by **steveL** » Sat Mar 08, 2014 4:53 am

Code: Select all

sys-libs/glibc-2.16.0        merge time: 30 minutes and 11 seconds.
sys-devel/gcc-4.7.3-r1       merge time: 1 hour, 16 minutes and 11 seconds.

$ grep -F 'model name' /proc/cpuinfo 
model name      : Pentium(R) Dual-Core  CPU      E5200  @ 2.50GHz
model name      : Pentium(R) Dual-Core  CPU      E5200  @ 2.50GHz

NFC about kernel, never time it. I'll time next one, and see, though that does depend on config as well.

megaflow · Post by **megaflow** » Sat Mar 08, 2014 3:18 pm

kernel build less then 5 min with the -j8 flag

genlop -t glibc gcc
* sys-libs/glibc

Sat Feb 8 05:06:00 2014 >>> sys-libs/glibc-2.17
merge time: 7 minutes and 20 seconds.

* sys-devel/gcc

Sat Feb 8 05:26:11 2014 >>> sys-devel/gcc-4.7.3-r1
merge time: 20 minutes and 11 seconds.

grep -F 'model name' /proc/cpuinfo
model name : Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz
model name : Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz
model name : Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz
model name : Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz
model name : Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz
model name : Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz
model name : Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz
model name : Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz

Post by **NeddySeagoon** » Sat Mar 08, 2014 3:38 pm

Code: Select all

$ sudo genlop -t glibc gcc 
Password: 
 * sys-libs/glibc

     Sun May 12 20:22:56 2013 >>> sys-libs/glibc-2.17
       merge time: 3 minutes and 34 seconds.

     Wed Feb 12 20:10:38 2014 >>> sys-libs/glibc-2.18-r1
       merge time: 4 minutes and 33 seconds.

 * sys-devel/gcc

     Sun May 12 19:07:41 2013 >>> sys-devel/gcc-4.7.2-r1
       merge time: 12 minutes and 55 seconds.

     Thu May 16 22:20:20 2013 >>> sys-devel/gcc-4.7.3
       merge time: 18 minutes and 53 seconds.

     Sat Oct  5 10:42:33 2013 >>> sys-devel/gcc-4.7.3-r1
       merge time: 13 minutes and 45 seconds.

     Thu Oct 24 19:32:44 2013 >>> sys-devel/gcc-4.8.1-r1
       merge time: 13 minutes and 55 seconds.

     Sun Dec  8 12:49:30 2013 >>> sys-devel/gcc-4.8.2
       merge time: 13 minutes and 36 seconds.

     Wed Feb 12 20:36:32 2014 >>> sys-devel/gcc-4.8.2
       merge time: 14 minutes.

roy@NeddySeagoon_Static ~ $  grep -F 'model name' /proc/cpuinfo 
model name      : AMD Phenom(tm) II X6 1090T Processor

I usually run emerge @system -uDNkav --jobs=2 --keep-going --with-bdeps=y with MAKEOPTS="-j8" and no ccache or distc helpers

jathlon · Post by **jathlon** » Sun Mar 09, 2014 4:47 am

glibc

Code: Select all

time emerge -1q glibc
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-libs/glibc-2.18-r1
>>> Installing (1 of 1) sys-libs/glibc-2.18-r1

<snippage>

real	2m28.516s
user	8m59.507s
sys	2m10.230s

gcc

Code: Select all

time emerge -1q gcc
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-devel/gcc-4.8.2
>>> Installing (1 of 1) sys-devel/gcc-4.8.2

<snippage>

real	10m40.940s
user	60m41.820s
sys	5m44.803s

kernel; My own kernel config. As minimal as I could make it, with my current understanding of the kernel options. Move .config out of the way, run mrproper, cp .config back into source directory run make -s oldconfig and..

Code: Select all

time make -s -j13 all
Setup is 15808 bytes (padded to 15872 bytes).
System is 2790 kB
CRC 54039f11
Kernel: arch/x86/boot/bzImage is ready  (#1)

real	1m16.138s
user	12m46.581s
sys	1m11.347s

Hardware

linux # uname -p
Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz

Running on a P9X79-Pro with performance selected in the bios. So i7z is saying it's running about 4.17 GHz. I've never seen it go over 70C in lm_sensors.

joe

eccerr0r · Post by **eccerr0r** » Fri Mar 14, 2014 10:24 pm

rudregues wrote:kernel less than 5 minutes (I use seeds), the others:

Yeah, this kind of makes the kernel compile times meaningless, unless people use the same .config it's hard to compare...

I compile most if not all USB drivers and that adds a lot to the kernel build times. I know a lot of people probably compile only things they have and nothing more. I just got tired of having to rebuild kernels (and possibly needing a reboot) when I get some sort of random hardware, so I just paid it forward and built a lot of modules.

I've had kernel build times from around 1 minute (dual celeron 450 with ~2.0 kernel) to 5 hours (386-40 with 0.99pl12 kernel, 4MB), it's been a long ride with lots of different machines. Right now it's somewhere in between...

szpko · Post by **szpko** » Sat Apr 26, 2014 5:30 am

Haswell

Code: Select all

# genlop -t glibc gcc 
----
sys-libs/glibc-2.19 USE="gd (multilib)" 
merge time: 3 minutes and 23 seconds.

sys-devel/gcc-4.8.2 USE="awt cxx fortran gcj graphite (multilib) nls nptl openmp"
merge time: 14 minutes and 16 seconds.
----

Code: Select all

# eselect java-vm show
----
icedtea-7 
----

Code: Select all

# grep -F 'model name' /proc/cpuinfo 
----
model name	: Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz
----

Code: Select all

# cat /etc/make.conf
----
CFLAGS="-march=native -O2 -pipe"
EMERGE_DEFAULT_OPTS="--quiet --verbose --jobs=8 --load-average=8 --with-bdeps=y --autounmask-write=y"
MAKEOPTS="-j8"
----

Code: Select all

# make mrproper && time make -j8
----
| real 0m48.436s | user 5m24.677s | sys 0m14.904s |
----

warrens · Post by **warrens** » Sat Apr 26, 2014 6:24 am

Code: Select all

# uname -a 
Linux localhost 3.14.0-gentoo #3 SMP PREEMPT Sat Apr 12 14:12:56 CDT 2014 x86_64 Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz GenuineIntel GNU/Linux

Code: Select all

# genlop -t gcc glibc -f /mnt/gentoo/var/log/emerge.log 
using logfile /mnt/gentoo/var/log/emerge.log
 * sys-devel/gcc

     Fri Apr 25 18:44:12 2014 >>> sys-devel/gcc-4.8.2
       merge time: 22 minutes and 41 seconds.

 * sys-libs/glibc

     Fri Apr 25 14:16:53 2014 >>> sys-libs/glibc-2.19
       merge time: 8 minutes and 25 seconds.

About 4 minutes for the kernel with make -j12

All this with KDE up and running and several apps open.

Irre · Post by **Irre** » Sat Apr 26, 2014 6:37 am

Not that fast.

Code: Select all

localhost ~ # genlop -t glibc
 * sys-libs/glibc

     Wed Jan 29 19:35:19 2014 >>> sys-libs/glibc-2.18-r1
       merge time: 8 hours, 14 minutes and 1 second.

     Thu Apr 17 18:21:57 2014 >>> sys-libs/glibc-2.19
       merge time: 6 hours, 14 minutes and 51 seconds.

localhost ~ # genlop -t gcc
 * sys-devel/gcc

     Fri Jan 31 00:21:40 2014 >>> sys-devel/gcc-4.8.2
       merge time: 1 day, 2 hours, 26 minutes and 10 seconds.

Linux localhost 3.9.10-raspberrypi-r20130715 #1 PREEMPT Sun Nov 10 23:06:15 CET 2013 armv6l BCM2708 GNU/Linux

mv · Post by mv » Sat Apr 26, 2014 7:39 am

aCOSwt wrote:

Code: Select all

acoswt@PrimaPratica /etc/portage $ cat /etc/portage/env/sys-devel/gcc
GCC_MAKE_TARGET="profiledbootstrap"

gcc docuimentation clearly states that this is not supported with parallel build. Is that documentation outdated or is there another reason why you do not put MAKEOPTS=-j1 here?

aCOSwt · Post by **aCOSwt** » Sat Apr 26, 2014 9:14 am

mv wrote:
aCOSwt wrote:
Code: Select all
acoswt@PrimaPratica /etc/portage $ cat /etc/portage/env/sys-devel/gcc
GCC_MAKE_TARGET="profiledbootstrap"
gcc docuimentation clearly states that this is not supported with parallel build. Is that documentation outdated or is there another reason why you do not put MAKEOPTS=-j1 here?

That documentation is not outdated (Last modified 2014-01-03), but I am lazy and since the eclass takes care of that already...

toolchain.eclass wrote:

Code: Select all

    # the gcc docs state that parallel make isnt supported for the
    # profiledbootstrap target, as collisions in profile collecting may occur.
    # boundschecking also seems to introduce parallel build issues.
    if [[ ${GCC_MAKE_TARGET} == "profiledbootstrap" ]] ||
       use_if_iuse boundschecking
    then
        export MAKEOPTS="${MAKEOPTS} -j1"
    fi

trippels · Post by **trippels** » Sat Apr 26, 2014 9:47 am

mv wrote:
aCOSwt wrote:
Code: Select all
acoswt@PrimaPratica /etc/portage $ cat /etc/portage/env/sys-devel/gcc
GCC_MAKE_TARGET="profiledbootstrap"
gcc docuimentation clearly states that this is not supported with parallel build. Is that documentation outdated or is there another reason why you do not put MAKEOPTS=-j1 here?

The documentation is wrong. You can profilbootstrap gcc in parallel at least since 4.6.

aCOSwt · Post by **aCOSwt** » Sat Apr 26, 2014 1:42 pm

trippels wrote:The documentation is wrong. You can profilbootstrap gcc in parallel at least since 4.6.

Yet another belief or do you hold "These pages are maintained by the GCC team. Last modified 2014-01-03." for a disgraceful decorating idea ?

trippels · Post by **trippels** » Sat Apr 26, 2014 1:52 pm

aCOSwt wrote:
trippels wrote:The documentation is wrong. You can profilbootstrap gcc in parallel at least since 4.6.
Yet another belief or do you hold "These pages are maintained by the GCC team. Last modified 2014-01-03." for a disgraceful decorating idea ?

That page gets automatically updated from gcc/doc/install.texi. I will post a patch to remove the sentence.

aCOSwt · Post by **aCOSwt** » Sat Apr 26, 2014 3:36 pm

trippels wrote:That page gets automatically updated from gcc/doc/install.texi. I will post a patch to remove the sentence.

Who am I for interfering between two Markus.
I respectfully withdraw...
... and patch my eclass...
and thank.

amulet_linux · Post by **amulet_linux** » Sat Apr 26, 2014 7:16 pm

glib
merge time: 9 minutes and 35 seconds.

gcc
merge time: 3 hours, 48 minutes and 10 seconds.

Processor Intel Atom

krinn · Post by **krinn** » Sun Apr 27, 2014 5:45 am

amulet_linux wrote:glib
merge time: 9 minutes and 35 seconds.

I don't want ruin your fun but add a "c" at end of glib and you might not like the timing result

eccerr0r · Post by **eccerr0r** » Sun Apr 27, 2014 8:21 am

Ouch... Atom... (I run Gentoo on one too...)

I feel... or maybe not... for those running native toolchain/Gentoo on ARM machines...

aCOSwt · Post by **aCOSwt** » Sun Apr 27, 2014 2:42 pm

trippels wrote:That page gets automatically updated from gcc/doc/install.texi. I will post a patch to remove the sentence.

Installing GCC: Building wrote:Unlike standard bootstrap, several additional restrictions apply. The compiler used to build stage1 needs to support a 64-bit integral type. It is recommended to only use GCC for this. Also parallel make is currently not supported since collisions in profile collecting may occur.
These pages are maintained by the GCC team. Last modified 2014-01-03.

Now reads:

Installing GCC: Building wrote:Unlike standard bootstrap, several additional restrictions apply. The compiler used to build stage1 needs to support a 64-bit integral type. It is recommended to only use GCC for this.
These pages are maintained by the GCC team. Last modified 2014-04-27.

Reverent gratefulness, trippels!

amulet_linux · Post by **amulet_linux** » Sun Apr 27, 2014 7:22 pm

krinn wrote:
amulet_linux wrote:glib
merge time: 9 minutes and 35 seconds.
I don't want ruin your fun but add a "c" at end of glib and you might not like the timing result

2 hours, 19 minutes and 49 seconds.

hahaha, that's true

amulet_linux · Post by **amulet_linux** » Sun Apr 27, 2014 7:28 pm

eccerr0r wrote:Ouch... Atom... (I run Gentoo on one too...)

I feel... or maybe not... for those running native toolchain/Gentoo on ARM machines...

Also I'm using KDE