On Fri, 04 Apr 2014 00:54:24 +0200, Martin Costabel
<costa...@wanadoo.fr> wrote:
On 3/04/14 01:27, Mark D. McKean wrote:
> > On 4/2/14, 5:38 pm, Daniel Macks wrote:
> >> But "one on the previous tools" is new information. Anyone with ideas is
> >> welcome to contribute, anyone who wants to fix it is welcome to assist.
>
> webkit-1.0.2-1.2.7-5 does not build for me with the latest xcode
> either. Thsi is 5-year-old code, so it isn't surprising that it has
> more and more problems with up-to-date OS and compiler versions.
> There are several different problems mentioned on the list. The one
> shown here
>
> []
> >
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/cctype:50:72:
> > error:
> > use of undeclared identifier
> >
> >
> 'isalnum_WTF_Please_use_ASCIICType_instead_of_ctype_see_comment_in_ASCIICType_h'
> > inline _LIBCPP_INLINE_VISIBILITY int __libcpp_isalnum(int __c) {return
> > isalnum(...
> > ^
> > ./JavaScriptCore/wtf/DisallowCType.h:57:17: note: expanded from macro
> > 'isalnum'
> > #define isalnum isalnum_WTF_Please_use_ASCIICType_instead_of_ctype_see_c...
>
> comes from libc++ on MacOSX 10.9. I don't know why it was not an
> error on 10.9 back in December.
>
> The other one was shown by Stefan Bruda:
>
> > In file included from WebCore/css/CSSComputedStyleDeclaration.cpp:24:
> > ./WebCore/css/CSSComputedStyleDeclaration.h:36:52: error: friend
> declaration specifying a default
> > argument must be a definition
> > friend PassRefPtr<CSSComputedStyleDeclaration>
> computedStyle(PassRefPtr<Node>, bool allo...
> > ^
> > ./WebCore/css/CSSComputedStyleDeclaration.h:76:48: error: friend
> declaration specifying a default
> > argument must be the only declaration
> > inline PassRefPtr<CSSComputedStyleDeclaration>
> computedStyle(PassRefPtr<Node> node, bool all...
> > ^
> > ./WebCore/css/CSSComputedStyleDeclaration.h:36:52: note: previous
> declaration is here
> > friend PassRefPtr<CSSComputedStyleDeclaration>
> computedStyle(PassRefPtr<Node>, bool allo...
>
> This one comes from the growing intolerance of clang and wasn't
> forbidden in the previous version of xcode.
> I am seeing both of these errors, too.
>
> I have also a patch for both of them that allows me to build
> webkit-1.0.2. I think the patch is non-toxic for previous build tools
> and OS versions, so I am just checking it in to CVS and wait what
> happens (webkit-1.0.2-1.2.7-6) :-)
Thanks!
dan
--
Daniel Macks
dma...@netspace.org
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Fink-users mailing list
Fink-users@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.macosx.fink.user
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users
