[Webkit-unassigned] [Bug 175040] New: WebKitEnumTypes.h:27:0: error: unterminated #ifndef WEBKIT_ENUM_TYPES_H

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Aug 1 12:10:30 PDT 2017


            Bug ID: 175040
           Summary: WebKitEnumTypes.h:27:0: error: unterminated #ifndef
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit Gtk
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: berto at igalia.com
                CC: bugs-noreply at webkitgtk.org

I'm having this build failure with WebKitGTK+ 2.17.5, and it has also been reported with 2.16.6:

   In file included from Source/WebKit/UIProcess/API/glib/WebKitCookieManager.cpp:26:0:
   obj-aarch64-linux-gnu/DerivedSources/webkit2gtk/webkit2/WebKitEnumTypes.h:27:0: error: unterminated #ifndef

That header is incomplete, and that happens because glib-mkenums fails
when generating it with the following error:

   Traceback (most recent call last):
     File "/usr/bin/glib-mkenums", line 669, in <module>
     File "/usr/bin/glib-mkenums", line 406, in process_file
       line = curfile.readline()
     File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
       return codecs.ascii_decode(input, self.errors)[0]
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 3887: ordinal not in range(128)

My locale is set to POSIX, and that's probably why this fails (reminds
me of bug 128971). The problem here is that the program this time is
glib-mkenums, so we cannot apply the same solution (unless we report
the problem there).

It looks like the non-ascii character that is causing trouble is this
'—' in WebKitWebContext.h:

   of web views and the content of in each must not interfere with the
   rest — for example a full-fledged web browser with support for
   multiple tabs.

so perhaps replacing it with an ascii '-' is enough to fix this. I'll
check it and come back with my findings.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170801/4b38197c/attachment.html>

More information about the webkit-unassigned mailing list