In the next 3 weeks I'll be on vacations back in Portugal. I'm afraid that I'll slow down a little since I'll spend most of my time with my friends and family (especially my girlfriend, who would strangle me to death if she caught me playing around with the computer on vacations! :-) This also means that I won't have permanent internet connection, and that I'll answer to emails just on the economic period (which is more or less at the same time that the IRC meetings have been).
I'll leave my workstation here at the university running but I just recently knew that there will be some remodeling on our office during my absence, which probably means that the workstation will be down from 25th Mar until my return on 7th Apr... Until then I hope to get the SourceForge compiler farm to make the snapshots instead. I've been reading about how to do that, and it's more or less straightforward. In principle I could just transfer my scripts and crontab it would be done, but unfortunately the SourceForge imposes some quota limits: 512MB hard quota, 256 soft quota. The compiled trunk takes 522 MB on my machine. For start, this means that I can't leave the build trees or even the source trees there - this poses no problem because the build tree is always almost completely rebuilt anyway, and the source tree should be really fast to get from CVS since it's in SourceForge CVS servers as well. Spite of that, I don't have space for a single build. One way to overcome this problem is to remove the '-g' debug info compiler option by applying systematically a patch to the source tree. This will surely reduce significantly the size of the build tree, and if we don't include '-s' strip linker option, we should still get a meaningful backtrace due to the COFF source line information, isn't it? Does anybody have any alternative idea? Regards, Jos� Fonseca _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
