From owner-freebsd-ports@freebsd.org Mon Nov 9 10:06:34 2015 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BCCF4A2AA46 for ; Mon, 9 Nov 2015 10:06:34 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from ainaz.pair.com (ainaz.pair.com [209.68.2.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9D41F157D for ; Mon, 9 Nov 2015 10:06:34 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from [192.168.0.129] (vie-91-186-144-215.dsl.sil.at [91.186.144.215]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ainaz.pair.com (Postfix) with ESMTPSA id 72A893F445; Mon, 9 Nov 2015 05:06:32 -0500 (EST) Date: Mon, 9 Nov 2015 11:06:30 +0100 (CET) From: Gerald Pfeifer To: Rainer Hurling cc: freebsd-ports@freebsd.org Subject: Re: lang/gcc48 fails to build In-Reply-To: <564040EE.6090504@gwdg.de> Message-ID: References: <564040EE.6090504@gwdg.de> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Nov 2015 10:06:34 -0000 Hi Rainer, On Mon, 9 Nov 2015, Rainer Hurling wrote: > I am using lang/gcc48 for a long time now on FreeBSD 11.0-CURRENT. From > time to time I have to rebuild the port. This is the first time, that I > get the following error: I have no idea where this is coming from. In fact, I rebuilt the lang/gcc port just last night (which is pretty much the same) and did not run into this. > Is this a known error? It seems, there is something odd with C++ mode > and C files? GCC now is built as C++ code, even though most source files have not been renamed from .c. So this warning is expected and can be ignored. This being an old port, nothing has changed on the GCC side. Which means something in -CURRENT must have broken it. Gerald