User forums > Nightly builds
The 25 June 2008 build (5106) is out.
Der Meister:
I can confirm this. The problem is the file defaults.cpp. Compiling it takes needs more that 1GB of RAM but on machines with less physical RAM (like mine, I have only 512MB here) a huge amount of swap space will be used which slows the computer down or makes it even unusable. After about five minutes I aborted the compiler and decided not to compile this plugin.
PsYhLo:
i have 2GB ram and 1GB swap :shock:
:lol:
edit
sorry that was offtopic :)
what is causing this
Jenna:
--- Quote from: PsYhLo on July 10, 2008, 10:03:23 am ---when i try to compile svn 5116 my HDD freaks out at Headerfixup when it trys to make the .o file
weird isn't it
only hdd work the cpu is in idle mod
this is causing on linux
--- End quote ---
I have 3.3 GB usable Ram and the 64-bit compilation uses about 3.4 GB for "defaults.cpp". Compiling for 32-bit uses much less memory.
This only happens with "./configure make ..." not when compiling with C::B.
And it does not start with r5116.
MortenMacFly:
--- Quote from: jens on July 10, 2008, 11:33:34 am ---This only happens with "./configure make ..." not when compiling with C::B.
--- End quote ---
Well, *that* is interesting... But I have no clue why this happens. If you look into the code it's pretty much simple. Why GCC freaks out?! I don't know. Any what's most strange is why this does not happen when compiling with C::B itself because the GCC call should in fact be exactly the same when compiling this file. Well - where to go from here? I won't undo the changes in SVN. Whoever has issues compiling just use C::B for compiling or leave out this plugin. I believe there should be a mystic disable-plugin=headerfixup switch or something... I don't know I am not a make guy (anymore... this cost me too much hairs in the past ;-)). Probably we will remove this plugin from the make system.
It also seems to work with different compiler(s). Probably splitting up the file even more could be another option (but would be stupid to "fix" a compiler bug...?!). Finally the plans for this plugin are that actually these values are read from a file at run-time. But this is a long-term change and may make not even sense...
Der Meister:
--- Quote from: MortenMacFly on July 10, 2008, 09:30:59 pm ---I believe there should be a mystic disable-plugin=headerfixup switch or something... I don't know I am not a make guy (anymore... this cost me too much hairs in the past ;-)).
--- End quote ---
"--with-contrib-plugins=all,-headerfixup" is the way to go.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version