From owner-freebsd-x11@FreeBSD.ORG Fri May 25 20:46:32 2007 Return-Path: X-Original-To: freebsd-x11@freebsd.org Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 825BD16A469 for ; Fri, 25 May 2007 20:46:32 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 7493313C447 for ; Fri, 25 May 2007 20:46:32 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id EF7E41A3C19; Fri, 25 May 2007 13:47:35 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 82ED152E3B; Fri, 25 May 2007 16:46:31 -0400 (EDT) Date: Fri, 25 May 2007 16:46:31 -0400 From: Kris Kennaway To: Ivan Voras Message-ID: <20070525204631.GA85327@xor.obsecurity.org> References: <200705252035.20548.dejan.lesjak@ijs.si> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Cc: freebsd-x11@freebsd.org Subject: Re: Stuck compiling xf86ScanPci? X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 May 2007 20:46:32 -0000 On Fri, May 25, 2007 at 10:22:29PM +0200, Ivan Voras wrote: > Dejan Lesjak wrote: > > On Friday 25 May 2007 20:18:49 Ivan Voras wrote: > >> I have a weird problem compiling xorg-server on a recent 7-current on > >> i386 with gcc 4.2: the process is stuck compiling xf86ScanPci.c, the > >> compiler is just doing nothing, consuming more and more memory. > > > Yes, it's been reported on -stable@ as well IIRC. It will eventually compile > > the file though, assuming you don't run out of memory. > > Update: I've removed everything from /usr/local (so it's empty) and > tried again, and this time it passed (without eating memory). > > There were some unusual libraries in /usr/local/lib/compat, like > libthr.so (sorry, don't have the whole list) which I noticed because > they were marked schg and I had to clear the flag before deleting them. > I think this might have influenced the compiler because I had the same > situation before - old compat libraries in /usr/local/lib/compat getting > pulled in for a newly built port (which I believe is a serious error but > haven't explored further). This is not supposed to happen, and does not happen in any case of which I am aware, so if you have evidence this is occurring please let us know. Kris