Date: Wed, 10 Jan 2018 15:01:04 +0100 From: Jan Beich <jbeich@FreeBSD.org> To: Alexey Dokuchaev <danfe@FreeBSD.org> Cc: Dimitry Andric <dim@FreeBSD.org>, svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r458581 - in head/lang: gcc48 gcc49 gcc5 gcc5/files Message-ID: <zi5l-x17j-wny@FreeBSD.org> In-Reply-To: <20180110134845.GA94223@FreeBSD.org> (Alexey Dokuchaev's message of "Wed, 10 Jan 2018 13:48:45 %2B0000") References: <201801092208.w09M8jeq029512@repo.freebsd.org> <20180110134845.GA94223@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Alexey Dokuchaev <danfe@FreeBSD.org> writes: > On Tue, Jan 09, 2018 at 10:08:45PM +0000, Dimitry Andric wrote: > >> New Revision: 458581 >> URL: https://svnweb.freebsd.org/changeset/ports/458581 >> >> Log: >> Fix builds of lang/gcc{48,49,5} with clang 6.0.0 >> >> Since clang++ 6.0.0 now defaults to -std=gnu++14 (similar to g++ 6 and >> higher), building gcc48, gcc49 or gcc5 produce quite a number of >> "invalid suffix on literal; C++11 requires a space between literal and >> identifier" errors. This is because in many places, double quotes are >> directly followed by printf helper macros like HOST_WIDE_INT_PRINT. >> [...] >> >> Modified: >> head/lang/gcc48/Makefile >> head/lang/gcc49/Makefile >> head/lang/gcc5/Makefile > > Does the fact that `lang/gcc47' is not part of this commit mean it is not > affected? Probably, yes. http://package18.nyi.freebsd.org/data/latest-per-pkg/gcc7/7.2.0_4/headamd64PR224669-default.log http://package18.nyi.freebsd.org/data/latest-per-pkg/gcc7/7.2.0_4/headi386PR224669-default.log
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?zi5l-x17j-wny>