Date: Mon, 21 Feb 2005 10:58:57 +0300 From: Vladimir Grebenschikov <vova@fbsd.ru> To: "current@freebsd.org" <current@freebsd.org> Cc: Marcel Moolenaar <marcel@xcllnt.net> Subject: Re: make(1) infinite loop on i386 Message-ID: <1108972737.1177.3.camel@localhost> In-Reply-To: <20050214182356.GA95737@xor.obsecurity.org> References: <20050214034034.GC43645@xor.obsecurity.org> <3fe948624c5583e9eb9c1150ae50b977@xcllnt.net> <20050214182356.GA95737@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
=F7 =D0=CE, 14/02/2005 =D7 10:23 -0800, Kris Kennaway =D0=C9=DB=C5=D4: >On Mon, Feb 14, 2005 at 12:08:13AM -0800, Marcel Moolenaar wrote: >> On Feb 13, 2005, at 7:40 PM, Kris Kennaway wrote: >>=20 >> >With a fresh build of 6.x, a lot of port builds are going into an >> >infinite loop and doing nothing. I think it's make(1) that is >> >looping. >>=20 >> Do you see this only on ia64? > >Looks like it's happening on amd64 as well (e.g. the ninja port is >causing make to infinitely loop on both arches). I have two ports that fails to build, after configure make starts eat 100% CPU for infinite time. It happens for www/apache2 and for lang/ruby18, all other ports upgraded ok. It does no syscalls, just eat CPU. No special CPU options while make build. Recent current and recent port-tree. Any suggestions ? --=20 Vladimir B. Grebenchikov vova@fbsd.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1108972737.1177.3.camel>