From owner-freebsd-emulation@FreeBSD.ORG Wed Mar 10 19:49:17 2010 Return-Path: Delivered-To: emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3BB22106566B for ; Wed, 10 Mar 2010 19:49:17 +0000 (UTC) (envelope-from decke@bluelife.at) Received: from mail.itac.at (mail.itac.at [91.205.172.9]) by mx1.freebsd.org (Postfix) with ESMTP id B6DB58FC13 for ; Wed, 10 Mar 2010 19:49:16 +0000 (UTC) Received: from [91.205.172.21] (helo=webmail.bluelife.at) by mail.itac.at with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1NpRu7-0001fP-7V; Wed, 10 Mar 2010 20:49:15 +0100 MIME-Version: 1.0 Date: Wed, 10 Mar 2010 20:49:16 +0100 From: Bernhard Froehlich To: Bill Moran In-Reply-To: <20100310112053.8afb9d01.wmoran@potentialtech.com> References: <20100310112053.8afb9d01.wmoran@potentialtech.com> Message-ID: <113836e22c55a3cb8337e7829e4deae9@bluelife.at> X-Sender: decke@bluelife.at User-Agent: RoundCube Webmail/0.3.1 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 X-Spam-Score: 0.9 (/) X-Spam-Report: Spam detection software, running on the system "mail.itac.at", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: On Wed, 10 Mar 2010 11:20:53 -0500, Bill Moran wrote: > I sent the information to the maintainer but haven't heard back yet. > Don't know how busy they are, or if they're on holiday or whatever. [...] Content analysis details: (0.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP 3.4 FH_DATE_PAST_20XX The date is grossly in the future. -1.0 AWL AWL: From: address is in the auto white-list Cc: emulation@freebsd.org Subject: Re: Fw: VirtualBox coredump on FreeBSD 8 during build X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Mar 2010 19:49:17 -0000 On Wed, 10 Mar 2010 11:20:53 -0500, Bill Moran wrote: > I sent the information to the maintainer but haven't heard back yet. > Don't know how busy they are, or if they're on holiday or whatever. beat is at the AsiaBSDCon and i am very busy at the company so i had no time to look at it yet. > In any event, I'm reposting this here, in the hopes that someone else > has seen this problem and can make a recommendation. > > Begin forwarded message: > > [snip] > > Checking for Xcursor: found, OK. > Checking for Xmu: found, OK. > Checking for Mesa / GLU: Segmentation fault (core dumped) > ===> Script "configure" failed unexpectedly. > Please report the problem to vbox@FreeBSD.org [maintainer] and attach the > "/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.2_OSE/config.log" > including the output of the failure of your make command. Also, it might be > a good idea to provide an overview of all packages installed on your system > (e.g. an `ls /var/db/pkg`). > *** Error code 1 > > Stop in /usr/ports/emulators/virtualbox-ose. > *** Error code 1 I think we had a similar report a long time ago. There should be a configure.log or a similar logfile that got created and logs all configure tests. Please send the last 50 lines of it so that i can have a look what actually fails. For the record it would be interesting what graphic driver you use. Is it possible that you use X11 Forwarding so your DISPLAY variable is set? That is a known problem and there also exists a Gentoo Bugreport about it (http://bugs.gentoo.org/268227) that recommends to unset the DISPLAY variable first before compiling virtualbox. Could you please also check first if all your ports (especially mesa and xorg) are up to date? Just to be sure that it's not a known mesa/x11 bug that was already fixed. Thanks! -- Bernhard Fröhlich http://www.bluelife.at/