From owner-freebsd-ports@FreeBSD.ORG Fri Aug 6 21:12:21 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 0565816A4CE for ; Fri, 6 Aug 2004 21:12:21 +0000 (GMT) Received: from lilzmailso01.liwest.at (lilzmailso01.liwest.at [212.33.55.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0DBF43D46 for ; Fri, 6 Aug 2004 21:12:20 +0000 (GMT) (envelope-from dgw@liwest.at) Received: from cm248-230.liwest.at ([81.10.248.230]) by lilzmailso01.liwest.at with esmtp (Exim 4.24) id 1BtC0b-0005GF-80; Fri, 06 Aug 2004 23:12:13 +0200 From: Daniela To: Volker Stolz Date: Fri, 6 Aug 2004 22:06:06 +0000 User-Agent: KMail/1.5.3 References: <200408052225.40246.dgw@liwest.at> <20040806083035.GA67718@i2.informatik.rwth-aachen.de> In-Reply-To: <20040806083035.GA67718@i2.informatik.rwth-aachen.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200408062206.06576.dgw@liwest.at> cc: ports@freebsd.org Subject: Re: graphics/aqsis: Doesn't compile, but found workaround X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: dgw@liwest.at List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Aug 2004 21:12:21 -0000 On Friday 06 August 2004 08:30, Volker Stolz wrote: > In local.freebsd-ports, you wrote: > > The port graphics/aqsis doesn't compile because of an internal compiler > > bug. A quick workaround is to compile with GCC 3.2 (maybe other versions > > work too, but I tried this one). There is still the problem that, at a > > later point, it fails because of an undefined reference to > > pthread_mutex_destroy and pthread_mutex_init. I solved it by adding > > -pthread to the command line. > > I'll try to look into this, but I remember trying to unbreak aqsis not too > long ago and gave up because something wasn't as straight forward as it > looked. Anyway, could you please use send-pr to submit a ports-bug with the > description above so we have a copy in memory that is more stable than > mine? Done. It's ports/70099.