You can see that it goes from 20 mins to 7 hours!Everything else compiles as expected.
I'm compiling in RAM (6g tmpfs mounted in RAM).
Any ideas guys what is causing this, what should i check on my system ?
Thank you!

EDIT: I reconfigured my kernel recently, may be I'm missing some .config options ?_________________"Dear Enemy: may the Lord hate you and all your kind, may you be turned orange in hue, and may your head fall off at an awkward moment."
"Linux is like a wigwam - no windows, no gates, apache inside..."

To make IcedTea compile on disk but everything else in tmpfs, you can use this trick (Example 2) using /etc/portage/env_________________“And even in authoritarian countries, information networks are helping people discover new facts and making governments more accountable.”– Hillary Clinton, Jan. 21, 2010

I would be very happy if someone could give me some further advice how to get back to 20 minutes compilation time (are those two hours icedtea-7 specific? )_________________"Dear Enemy: may the Lord hate you and all your kind, may you be turned orange in hue, and may your head fall off at an awkward moment."
"Linux is like a wigwam - no windows, no gates, apache inside..."

Of course, this is a quad core i7 with oodles of memory (10 parallel jobs). But still,

BTW, got irked with Oracle changing the licence and switched to icedtea during the weekend. WebCT is my main application that uses java heavily (course management system at our University) and it seems to work just fine._________________Sam

Well after i borked my root partition i decided to make a clean install for a change (instead of restoring from backup).
Compiling icedtea in RAM takes the same time >2 hours but memory usage does not exceed 2gb (my tmpfs is 6gb), so i decided to use icedtea-bin instead.
Thank you guys for your cooperation on this subject!_________________"Dear Enemy: may the Lord hate you and all your kind, may you be turned orange in hue, and may your head fall off at an awkward moment."
"Linux is like a wigwam - no windows, no gates, apache inside..."

The icedtea build allows to compile the final jdk with itself. Often this is forced on or off but sometimes it's optional.

Do you have a suggestion for such a use flag name for the cases where it is optional?

'java_enable_final_build' sounds good to me, or may be a make.conf line like this:

Code:

JAVA_ENABLE_FINAL_BUILD='y'

_________________"Dear Enemy: may the Lord hate you and all your kind, may you be turned orange in hue, and may your head fall off at an awkward moment."
"Linux is like a wigwam - no windows, no gates, apache inside..."

I would expect the build time to drop to something like 30 minutes for you if the flag is disabled.

A more serious suggestion would be 'bootstrap', what it technically is. So this has the potential if reading the local use description people will put it into make.conf. Which generally is a bad idea to do globally.

I would expect the build time to drop to something like 30 minutes for you if the flag is disabled.

A more serious suggestion would be 'bootstrap', what it technically is. So this has the potential if reading the local use description people will put it into make.conf. Which generally is a bad idea to do globally.

May be 'jbootstrap' ?
I just don't want it to be confused with the other 'bootstrap' useflag :

Code:

bootstrap - !!internal use only!! DO NOT SET THIS FLAG YOURSELF!, used during original system bootstrapping [make stage2]

I'm 100% sure that someone will be tempted to use it globally ._________________"Dear Enemy: may the Lord hate you and all your kind, may you be turned orange in hue, and may your head fall off at an awkward moment."
"Linux is like a wigwam - no windows, no gates, apache inside..."

I was just thinking to myself "why does this take so long?". Then I found this thread. I do the bootstrapping thing. Is that what is actually taking so long with IcedTea 7? There is certainly room to optimize the build times on their end. Or maybe JDKs these days are just too big.