svn commit: r458581 - in head/lang: gcc48 gcc49 gcc5 gcc5/files

[Dimitry Andric]

On 10 Jan 2018, at 14:48, Alexey Dokuchaev <danfe at FreeBSD.org> wrote:
> 
> 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?

No, not by default: from gcc 4.8 onwards, most parts of gcc are compiled
as C++, so that is the situation where the above issues occur.

Before that, you had to enable building with a C++ compiler using
ENABLE_BUILD_WITH_CXX, but at the time it was an experimental option.

See also:
  https://gcc.gnu.org/wiki/cxx-conversion
  https://gcc.gnu.org/ml/gcc/2012-08/msg00015.html

-Dimitry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 223 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.freebsd.org/pipermail/svn-ports-all/attachments/20180110/77e8777e/attachment.sig>