Date: Mon, 21 Feb 2005 09:03:45 +0100 (CET) From: Harti Brandt <hartmut.brandt@dlr.de> To: Vladimir Grebenschikov <vova@fbsd.ru> Cc: Marcel Moolenaar <marcel@xcllnt.net> Subject: Re: make(1) infinite loop on i386 Message-ID: <20050221090140.T34171@beagle.kn.op.dlr.de> In-Reply-To: <1108972737.1177.3.camel@localhost> References: <20050214034034.GC43645@xor.obsecurity.org> <20050214182356.GA95737@xor.obsecurity.org> <1108972737.1177.3.camel@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 21 Feb 2005, Vladimir Grebenschikov wrote: VG>В пн, 14/02/2005 в 10:23 -0800, Kris Kennaway пишет: VG>>On Mon, Feb 14, 2005 at 12:08:13AM -0800, Marcel Moolenaar wrote: VG>>> On Feb 13, 2005, at 7:40 PM, Kris Kennaway wrote: VG>>> VG>>> >With a fresh build of 6.x, a lot of port builds are going into an VG>>> >infinite loop and doing nothing. I think it's make(1) that is VG>>> >looping. VG>>> VG>>> Do you see this only on ia64? VG>> VG>>Looks like it's happening on amd64 as well (e.g. the ninja port is VG>>causing make to infinitely loop on both arches). VG> VG>I have two ports that fails to build, after configure make starts eat VG>100% CPU for infinite time. It happens for www/apache2 and for VG>lang/ruby18, all other ports upgraded ok. VG> VG>It does no syscalls, just eat CPU. No special CPU options while make VG>build. VG>Recent current and recent port-tree. VG> VG>Any suggestions ? That problem was fixed if you have a usr.bin/make/main.c newer than 1.117. Are you sure that you actually have a new make? harti
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050221090140.T34171>