Date: Thu, 6 Nov 2014 16:05:12 +0100 (CET) From: Gerald Pfeifer <gerald@pfeifer.com> To: Bryan Drewery <bdrewery@FreeBSD.org> Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r372094 - head/lang/gcc5 Message-ID: <alpine.LSU.2.11.1411061551400.2724@tuna.site> In-Reply-To: <545AC939.5060706@FreeBSD.org> References: <201411030619.sA36Jcpc094345@svn.freebsd.org> <545AC939.5060706@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 2014-11-05 17:04, Bryan Drewery wrote:
>> Log:
>> Update to the 20141102 snapshot of GCC 5.0.
> Fails to build for me on 10.0 amd64:
I actually am using 10.1 as my primary test environment with nightly
builds and did not see the problem there.
Until a day ago (a day or two after that machine was updated to
10.1-PRERELEASE, not sure that is related).
>> In file included from .././../gcc-5-20141102/libcc1/plugin.cc:58:
>> In file included from /usr/include/c++/v1/string:433:
>> In file included from /usr/include/c++/v1/cwchar:107:
>> In file included from /usr/include/c++/v1/cwctype:54:
>> /usr/include/c++/v1/cctype:51:72: error: use of undeclared identifier
>> 'do_not_use_isalnum_with_safe_ctype'
>> inline _LIBCPP_INLINE_VISIBILITY int __libcpp_isalnum(int __c) {return
>> isalnum(__c);}
Does anyone know where this comes from and what do to about it?
What I am seeing may well be a regression upstream, though that
does not explain why my testing succeeded when I updated lang/gcc.
Gerald
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.LSU.2.11.1411061551400.2724>