OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: agosine on September 03, 2004, 06:48:39 pm
-
How long should it take to compile oemake opie-image on a P3 600MHz machine? Mine ran for 53+ hours and then failed. Will it always take that long? I've installed ccache and psyco. Not sure if they help. Specifically is there a way to speed glibc-2.3.2+cvs20040726-r9 up? I don't need every language.
-
How long should it take to compile oemake opie-image on a P3 600MHz machine? Mine ran for 53+ hours and then failed. Will it always take that long? I've installed ccache and psyco. Not sure if they help. Specifically is there a way to speed glibc-2.3.2+cvs20040726-r9 up? I don't need every language.
On my P4 2.8 with 1GB RAM oemake opie-image takes about 2 hours.
Anyways, i think 53 hours is a little bit extreme. I can only guess that you don't have a lot of RAM in that box so that your system is swapping like mad.
And i agree that compiling libc is a PITA
-
My PII 400 w. 64Mb RAM took 5.5 days, however I think it should have been quicker: I use a KVM switch to switch between my WinXP machine and the Linux box (at uni) and it appears that the double tap on scroll-lock (which is needed to change between the machines) was pausing the console on the Linux box - and therefore it didn't run until I switched back.
Possibly (I've not run exhaustive tests ;-) worth bearing in mind.
Si
-
Specifically is there a way to speed glibc-2.3.2+cvs20040726-r9 up? I don't need every language.
Yes I also thought this.
However if you set 'CVSDATE=20040726' (I think that's the right var.) in your local.conf you won't have to do it again after the first run through. Or you could edit the glibc.oe (I assume the name's something like that) to pass different arguments to ./configure.
Si