From owner-freebsd-ports@FreeBSD.ORG Wed Feb 11 05:48:05 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 018CD16A4CE for ; Wed, 11 Feb 2004 05:48:05 -0800 (PST) Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by mx1.FreeBSD.org (Postfix) with SMTP id C8CE943D2F for ; Wed, 11 Feb 2004 05:48:04 -0800 (PST) (envelope-from adamw@magnesium.net) Received: (qmail 44057 invoked by uid 1252); 11 Feb 2004 13:48:04 -0000 Date: 11 Feb 2004 08:48:04 -0500 Date: Wed, 11 Feb 2004 08:48:04 -0500 From: Adam Weinberger To: Edwin Culp Message-ID: <20040211134804.GJ3365@toxic.magnesium.net> References: <1076473818.59812.10.camel@current> <20040211045704.GF3365@toxic.magnesium.net> <20040211061140.o40o0cosk0skks0s@mail.viviendaatualcance.com.mx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040211061140.o40o0cosk0skks0s@mail.viviendaatualcance.com.mx> X-Editor: Vim 6.2 http://www.vim.org X-Mailer: Mutt 1.5 http://www.mutt.org X-URL: http://www.vectors.cx X-ASL: 6/m/behind you User-Agent: Mutt/1.5.4i cc: freebsd-ports@freebsd.org Subject: Re: qt-3.2.3 fails during configure, looking for qplatformdefs.h in wrong prefix? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Feb 2004 13:48:05 -0000 >> (02.11.2004 @ 0711 PST): Edwin Culp said, in 1.6K: << > ---> Session started at: Wed, 11 Feb 2004 06:02:56 -0600 > [Updating the pkgdb in /var/db/pkg ... - 301 packages > found > (-26 +17) (...)ruby in malloc(): error: allocation failed > Abort (core dumped) > > It's been a while since I've seen a malloc() error. Is anyone else seen > this > are am I just lucky :-) >> end of "Re: qt-3.2.3 fails during configure, looking for qplatformdefs.h in wrong prefix?" from Edwin Culp << Best as I can tell, this comes from 2 sessions of portupgrade or the like modifying the pkgdb.db at the same time. The command "pkgdb -fu" should fix the problem, but you should go get a cup of coffee while it's running ;;) # Adam -- Adam Weinberger adam@vectors.cx // adamw@FreeBSD.org // adamw@magnesium.net http://www.vectors.cx