WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
127283
[GTK] Fix a c++11 compliance issue for fontconfig
https://bugs.webkit.org/show_bug.cgi?id=127283
Summary
[GTK] Fix a c++11 compliance issue for fontconfig
ChangSeok Oh
Reported
2014-01-20 04:10:46 PST
A build failure happens when building with clang. In file included from ../../Source/WebCore/platform/graphics/freetype/FontPlatformDataFreeType.cpp:29: In file included from /home/shivamidow/Projects/WebKit/WebKitBuild/Dependencies/Root/include/cairo/cairo-ft.h:50: /home/shivamidow/Projects/WebKit/WebKitBuild/Dependencies/Root/include/fontconfig/fontconfig.h:116:39: error: invalid suffix on literal; C++11 requires a space between literal and identifier [-Wreserved-user-defined-literal] #define FC_CACHE_SUFFIX ".cache-"FC_CACHE_VERSION ^ /home/shivamidow/Projects/WebKit/WebKitBuild/Dependencies/Root/include/fontconfig/fontconfig.h:117:45: error: invalid suffix on literal; C++11 requires a space between literal and identifier [-Wreserved-user-defined-literal] #define FC_DIR_CACHE_FILE "fonts.cache-"FC_CACHE_VERSION ^ /home/shivamidow/Projects/WebKit/WebKitBuild/Dependencies/Root/include/fontconfig/fontconfig.h:118:47: error: invalid suffix on literal; C++11 requires a space between literal and identifier [-Wreserved-user-defined-literal] #define FC_USER_CACHE_FILE ".fonts.cache-"FC_CACHE_VERSION ^ CXX Source/WebCore/bridge/libWebCore_la-NP_jsobject.lo CXX Source/WebCore/bridge/libWebCore_la-npruntime.lo So I propose to apply a proper patch to fontconfig or else to bump fontconfig to at lease 2.9.91
Attachments
Patch
(2.92 KB, patch)
2014-01-20 04:19 PST
,
ChangSeok Oh
no flags
Details
Formatted Diff
Diff
Patch
(1.64 KB, patch)
2014-01-21 02:14 PST
,
ChangSeok Oh
no flags
Details
Formatted Diff
Diff
Patch
(2.90 KB, patch)
2014-01-21 09:16 PST
,
ChangSeok Oh
no flags
Details
Formatted Diff
Diff
Show Obsolete
(2)
View All
Add attachment
proposed patch, testcase, etc.
ChangSeok Oh
Comment 1
2014-01-20 04:19:10 PST
Created
attachment 221645
[details]
Patch
Martin Robinson
Comment 2
2014-01-20 09:53:52 PST
Is there any way we can instead compile fontconfig with -Wno-reserved-user-defined-literal
Zan Dobersek
Comment 3
2014-01-20 11:40:07 PST
Using module_autogenargs in Tools/gtk/jhbuildrc should work: module_autogenargs['fontconfig'] = 'CFLAGS=...' + autogenargs
Martin Robinson
Comment 4
2014-01-20 12:29:34 PST
Maybe we can wait for the alternate approach on this one so that we don't have to have another patch in the repo?
ChangSeok Oh
Comment 5
2014-01-21 02:14:41 PST
Created
attachment 221729
[details]
Patch
ChangSeok Oh
Comment 6
2014-01-21 02:16:31 PST
(In reply to
comment #2
)
> Is there any way we can instead compile fontconfig with -Wno-reserved-user-defined-literal
Yeah. we can avoid the failure by adding the flag, -Wno-reserved-user-defined-literal to CXXFALGS.
ChangSeok Oh
Comment 7
2014-01-21 02:18:37 PST
(In reply to
comment #3
)
> Using module_autogenargs in Tools/gtk/jhbuildrc should work: > > module_autogenargs['fontconfig'] = 'CFLAGS=...' + autogenargs
Zan thanks for the tip. But the build failure happens when building webkit not fontconfig itself. Sorry for my poor description about this bug. :P
Martin Robinson
Comment 8
2014-01-21 08:30:42 PST
(In reply to
comment #7
)
> (In reply to
comment #3
) > > Using module_autogenargs in Tools/gtk/jhbuildrc should work: > > > > module_autogenargs['fontconfig'] = 'CFLAGS=...' + autogenargs > > Zan thanks for the tip. But the build failure happens when building webkit not fontconfig itself. Sorry for my poor description about this bug. :P
Oh, in that case a patch is probably the best, because we don't want to let C++11 slip into WebKit code. Sorry for the confusion. Do you mind if I r+ your patch again?
ChangSeok Oh
Comment 9
2014-01-21 09:11:26 PST
(In reply to
comment #8
)
> (In reply to
comment #7
) > > (In reply to
comment #3
) > > > Using module_autogenargs in Tools/gtk/jhbuildrc should work: > > > > > > module_autogenargs['fontconfig'] = 'CFLAGS=...' + autogenargs > > > > Zan thanks for the tip. But the build failure happens when building webkit not fontconfig itself. Sorry for my poor description about this bug. :P > > Oh, in that case a patch is probably the best, because we don't want to let C++11 slip into WebKit code. Sorry for the confusion. Do you mind if I r+ your patch again?
No problem. Let me re-upload the first patch near soon. :)
ChangSeok Oh
Comment 10
2014-01-21 09:16:35 PST
Created
attachment 221752
[details]
Patch
ChangSeok Oh
Comment 11
2014-01-21 09:50:26 PST
Comment on
attachment 221752
[details]
Patch Thanks for the r+!
WebKit Commit Bot
Comment 12
2014-01-21 10:18:30 PST
Comment on
attachment 221752
[details]
Patch Clearing flags on attachment: 221752 Committed
r162448
: <
http://trac.webkit.org/changeset/162448
>
WebKit Commit Bot
Comment 13
2014-01-21 10:18:33 PST
All reviewed patches have been landed. Closing bug.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug