Date: Thu, 06 Dec 2007 16:17:25 +0100 From: Jan Lentfer <Jan.Lentfer@web.de> To: Nikos Ntarmos <ntarmos@ceid.upatras.gr> Cc: freebsd-current@freebsd.org Subject: Re: Problems Building 7.0-Beta3 with -Os Message-ID: <20071206161725.1wrnizqd0gcg44sk@neslonek.homeunix.org> In-Reply-To: <20071206065911.GA55397@ace.netcins.ceid.upatras.gr> References: <4756BAD3.4060905@web.de> <20071206020033.GB83604@ace.netcins.ceid.upatras.gr> <47579348.3090709@web.de> <20071206065911.GA55397@ace.netcins.ceid.upatras.gr>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Nikos, Zitat von Nikos Ntarmos <ntarmos@ceid.upatras.gr>: > [...] > 1 1 0 623384 174992 43861 0 0 0 92 0 0 0 1299 138 347 43 57= 0 >>>>> Compilation break > 0 0 0 70200 711396 2515 0 0 0 136608 0 9 0 1257 453 =20 > 281 9 91 0 > ^^^^^^ ^^^^^^ > > Funny how 'avm' and 'fre' are lower/higher by almost the same amout your > max dataseg is after the compilation break... Do you have a swap > partition? If you do, perhaps you should try bumping kern.maxdsiz and > kern.maxssiz in /boot/loader.conf and see what happens... (e.g. try with > kern.maxdsiz=3D"896M" and kern.maxssiz=3D"256M" with 1G RAM and another 1G > swap). Also, what is the value of kern.maxusers? With your suggested settings it works now - thank you very much. =20 Compilation hasn't totally finished yet, but I got far past the point =20 where it broke off before. Still I find this quite strange behavior, =20 but this seems to be rather a gcc thing than a FBSD problem, right? Kind Regards, ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071206161725.1wrnizqd0gcg44sk>