From owner-freebsd-ports@FreeBSD.ORG Sun Apr 19 10:00:20 2009 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A95061065673 for ; Sun, 19 Apr 2009 10:00:20 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.131.111.2]) by mx1.freebsd.org (Postfix) with ESMTP id 683A48FC14 for ; Sun, 19 Apr 2009 10:00:20 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from acrux.dbai.tuwien.ac.at (acrux [128.131.111.60]) by vexpert.dbai.tuwien.ac.at (Postfix) with ESMTP id 1349D3910C; Sun, 19 Apr 2009 12:00:18 +0200 (CEST) Received: by acrux.dbai.tuwien.ac.at (Postfix, from userid 1203) id B3F5B10059; Sun, 19 Apr 2009 12:00:19 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by acrux.dbai.tuwien.ac.at (Postfix) with ESMTP id A2B841003D; Sun, 19 Apr 2009 12:00:19 +0200 (CEST) Date: Sun, 19 Apr 2009 12:00:19 +0200 (CEST) From: Gerald Pfeifer To: Oliver Lehmann In-Reply-To: <20090409062738.65318.qmail@avocado.salatschuessel.net> Message-ID: References: <20090409062738.65318.qmail@avocado.salatschuessel.net> User-Agent: Alpine 1.99 (LSU 1142 2008-08-13) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: ports@FreeBSD.org Subject: Re: problems with lang/gcc43 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Apr 2009 10:00:20 -0000 Hi Oliver, On Thu, 9 Apr 2009, Oliver Lehmann wrote: > I've two problems with lang/gcc43. > 1) for me it appears not to be MAKE_JOBS_SAFE. I'm getting continous errors > compiling it on my dual PIII850 System: > http://files.pofo.de/gcc-4.3.4_20090326.log this is the only report of this kind that I have seen so far, both in the context of FreeBSD and in general. Many, if not most, GCC developers have been building GCC with -j2, -j4, or above (up to and including -j64 on true 64 core hardware as early as four years ago), on fast machines as well as environments that take days to build, and I would expect any issue like this to have come up in that context. Gerald -- Gerald (Jerry) Pfeifer gerald@pfeifer.com http://www.pfeifer.com/gerald/