[webkit-dev] Fwd: build-webkit stopped working for me
Is Snow Leopard deprecated? Dave (WebKit's MathML guy) is reporting trouble building the Apple Mac port on Snow Leopard. We don't seem to have a Snow Leopard bot on: http://build.webkit.org/console?category=AppleMac so it seems totally concievable that it's broken. If it is deprecated, I'm happy to post patches to remove support. :) -- Forwarded message -- From: Dave Barton dbar...@mathscribe.com I'm sorry to bug you guys, but I don't know who else to ask. After my last update-webkit, build-webkit --debug doesn't work for me. I tried asking in IRC but got no response. Below is some sample output. The script actually dies after failing to compile 7 files in JavaScriptCore: runtime/InitializeThreading.cpp runtime/Options.cpp heap/GCThreadSharedData.cpp heap/SlotVisitor.cpp heap/Heap.cpp heap/HeapStatistics.cpp heap/GCThread.cpp I am running on Snow Leopard, to try to stay compatible with another project (job). Has WebKit stopped supporting that for development? I haven't seen any notice on webkit-dev e-mail. I notice that on http://build.chromium.org/p/chromium.webkit/console the Mac OS 10.6 bots are failing, but they're failing tests not compiles. All 7 compile failures are at the same place, so I've included 2 below that together show how all 7 fail. At /usr/include/c++/4.2.1/bits/locale_classes.h:411, std::locale::facet::_M_remove_reference() (an internal C++ standard library function) does a try/catch, but the gcc-4.2 command includes -fno-exceptions. Do I need a later gcc (C++ standard library)? Is there a way to find out what WebKit supports/requires, or what the bots are using? Thanks very much for any help or pointers. If there's someone better for me to ask, please let me know. Take care, Dave B. === BUILD NATIVE TARGET JavaScriptCore OF PROJECT JavaScriptCore WITH CONFIGURATION Debug === Check dependencies ProcessInfoPlistFile /Users/drb/devel/WebKit/WebKitBuild/Debug/JavaScriptCore.framework/Versions/A/Resources/Info.plist Info.plist cd /Users/drb/devel/WebKit/Source/JavaScriptCore builtin-infoPlistUtility Info.plist -expandbuildsettings -platform macosx -o /Users/drb/devel/WebKit/WebKitBuild/Debug/JavaScriptCore.framework/Versions/A/Resources/Info.plist CompileC /Users/drb/devel/WebKit/WebKitBuild/JavaScriptCore.build/Debug/JavaScriptCore.build/Objects-normal/x86_64/Heap.o heap/Heap.cpp normal x86_64 c++ com.apple.compilers.gcc.4_2 cd /Users/drb/devel/WebKit/Source/JavaScriptCore setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fno-exceptions -fno-rtti -fpascal-strings -fasm-blocks -O0 -Werror -Wmissing-prototypes -Wnon-virtual-dtor -Wsign-compare -Wnewline-eof -DHAVE_DTRACE=1 -DWEBKIT_VERSION_MIN_REQUIRED=WEBKIT_VERSION_LATEST -DHAVE_HEADER_DETECTION_H -fstrict-aliasing -fvisibility=hidden -fvisibility-inlines-hidden -fno-threadsafe-statics -mmacosx-version-min=10.6 -gdwarf-2 -I/Users/drb/devel/WebKit/WebKitBuild/JavaScriptCore.build/Debug/JavaScriptCore.build/JavaScriptCore.hmap -Wall -Wextra -Wcast-qual -Wchar-subscripts -Wextra-tokens -Wformat=2 -Winit-self -Wmissing-format-attribute -Wmissing-noreturn -Wpacked -Wpointer-arith -Wredundant-decls -Wundef -Wwrite-strings -F/Users/drb/devel/WebKit/WebKitBuild/Debug -I/Users/drb/devel/WebKit/WebKitBuild/Debug/include -I/Users/drb/devel/WebKit/WebKitBuild/Debug/DerivedSources/JavaScriptCore -I. -Iicu -I/Users/drb/devel/WebKit/WebKitBuild/Debug/usr/local/include -I/Users/drb/devel/WebKit/WebKitBuild/JavaScriptCore.build/Debug/JavaScriptCore.build/DerivedSources/x86_64 -I/Users/drb/devel/WebKit/WebKitBuild/JavaScriptCore.build/Debug/JavaScriptCore.build/DerivedSources -include /var/folders/RC/RCYcW-YGHj0lsQvZo63kAk+++TM/-Caches-/com.apple.Xcode.502/SharedPrecompiledHeaders/JavaScriptCorePrefix-eomldsaqazlgrmgzqddxqhcetggy/JavaScriptCorePrefix.h -c /Users/drb/devel/WebKit/Source/JavaScriptCore/heap/Heap.cpp -o /Users/drb/devel/WebKit/WebKitBuild/JavaScriptCore.build/Debug/JavaScriptCore.build/Objects-normal/x86_64/Heap.o In file included from /usr/include/c++/4.2.1/bits/ios_base.h:47, from /usr/include/c++/4.2.1/ios:48, from /usr/include/c++/4.2.1/ostream:45, from /usr/include/c++/4.2.1/iterator:70, from /Users/drb/devel/WebKit/WebKitBuild/Debug/usr/local/include/wtf/Deque.h:36, from /Users/drb/devel/WebKit/Source/JavaScriptCore/heap/HeapStatistics.h:29, from /Users/drb/devel/WebKit/Source/JavaScriptCore/heap/Heap.cpp:31: /usr/include/c++/4.2.1/bits/locale_classes.h: In member function 'void std::locale::facet::_M_remove_reference() const': /usr/include/c++/4.2.1/bits/locale_classes.h:411: error: exception handling disabled, use -fexceptions to enable CompileC /Users/drb/devel/WebKit/WebKitBuild/JavaScriptCore.build/Debug/JavaScriptCore.build/Objects-normal/x86_64/GCThreadSharedData.o heap/GCThreadSharedData.cpp normal x86_64 c++
Re: [webkit-dev] build-webkit stopped working for me
Apple did not ship the last release of Safari to SnowLeopard and we have no plans to maintain SnowLeopard support on trunk. We haven't actively ripped out SL-specific ifdefs because we were under the impression that the Chromium port still targets SL and sometimes uses Mac code paths. That being said, the failures below look like compiler issues and may be fixable by updating to a newer toolchain. Cheers, Maciej On Oct 21, 2012, at 12:34 PM, Eric Seidel e...@webkit.org wrote: Is Snow Leopard deprecated? Dave (WebKit's MathML guy) is reporting trouble building the Apple Mac port on Snow Leopard. We don't seem to have a Snow Leopard bot on: http://build.webkit.org/console?category=AppleMac so it seems totally concievable that it's broken. If it is deprecated, I'm happy to post patches to remove support. :) -- Forwarded message -- From: Dave Barton dbar...@mathscribe.com I'm sorry to bug you guys, but I don't know who else to ask. After my last update-webkit, build-webkit --debug doesn't work for me. I tried asking in IRC but got no response. Below is some sample output. The script actually dies after failing to compile 7 files in JavaScriptCore: runtime/InitializeThreading.cpp runtime/Options.cpp heap/GCThreadSharedData.cpp heap/SlotVisitor.cpp heap/Heap.cpp heap/HeapStatistics.cpp heap/GCThread.cpp I am running on Snow Leopard, to try to stay compatible with another project (job). Has WebKit stopped supporting that for development? I haven't seen any notice on webkit-dev e-mail. I notice that on http://build.chromium.org/p/chromium.webkit/console the Mac OS 10.6 bots are failing, but they're failing tests not compiles. All 7 compile failures are at the same place, so I've included 2 below that together show how all 7 fail. At /usr/include/c++/4.2.1/bits/locale_classes.h:411, std::locale::facet::_M_remove_reference() (an internal C++ standard library function) does a try/catch, but the gcc-4.2 command includes -fno-exceptions. Do I need a later gcc (C++ standard library)? Is there a way to find out what WebKit supports/requires, or what the bots are using? Thanks very much for any help or pointers. If there's someone better for me to ask, please let me know. Take care, Dave B. === BUILD NATIVE TARGET JavaScriptCore OF PROJECT JavaScriptCore WITH CONFIGURATION Debug === Check dependencies ProcessInfoPlistFile /Users/drb/devel/WebKit/WebKitBuild/Debug/JavaScriptCore.framework/Versions/A/Resources/Info.plist Info.plist cd /Users/drb/devel/WebKit/Source/JavaScriptCore builtin-infoPlistUtility Info.plist -expandbuildsettings -platform macosx -o /Users/drb/devel/WebKit/WebKitBuild/Debug/JavaScriptCore.framework/Versions/A/Resources/Info.plist CompileC /Users/drb/devel/WebKit/WebKitBuild/JavaScriptCore.build/Debug/JavaScriptCore.build/Objects-normal/x86_64/Heap.o heap/Heap.cpp normal x86_64 c++ com.apple.compilers.gcc.4_2 cd /Users/drb/devel/WebKit/Source/JavaScriptCore setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fno-exceptions -fno-rtti -fpascal-strings -fasm-blocks -O0 -Werror -Wmissing-prototypes -Wnon-virtual-dtor -Wsign-compare -Wnewline-eof -DHAVE_DTRACE=1 -DWEBKIT_VERSION_MIN_REQUIRED=WEBKIT_VERSION_LATEST -DHAVE_HEADER_DETECTION_H -fstrict-aliasing -fvisibility=hidden -fvisibility-inlines-hidden -fno-threadsafe-statics -mmacosx-version-min=10.6 -gdwarf-2 -I/Users/drb/devel/WebKit/WebKitBuild/JavaScriptCore.build/Debug/JavaScriptCore.build/JavaScriptCore.hmap -Wall -Wextra -Wcast-qual -Wchar-subscripts -Wextra-tokens -Wformat=2 -Winit-self -Wmissing-format-attribute -Wmissing-noreturn -Wpacked -Wpointer-arith -Wredundant-decls -Wundef -Wwrite-strings -F/Users/drb/devel/WebKit/WebKitBuild/Debug -I/Users/drb/devel/WebKit/WebKitBuild/Debug/include -I/Users/drb/devel/WebKit/WebKitBuild/Debug/DerivedSources/JavaScriptCore -I. -Iicu -I/Users/drb/devel/WebKit/WebKitBuild/Debug/usr/local/include -I/Users/drb/devel/WebKit/WebKitBuild/JavaScriptCore.build/Debug/JavaScriptCore.build/DerivedSources/x86_64 -I/Users/drb/devel/WebKit/WebKitBuild/JavaScriptCore.build/Debug/JavaScriptCore.build/DerivedSources -include /var/folders/RC/RCYcW-YGHj0lsQvZo63kAk+++TM/-Caches-/com.apple.Xcode.502/SharedPrecompiledHeaders/JavaScriptCorePrefix-eomldsaqazlgrmgzqddxqhcetggy/JavaScriptCorePrefix.h -c /Users/drb/devel/WebKit/Source/JavaScriptCore/heap/Heap.cpp -o /Users/drb/devel/WebKit/WebKitBuild/JavaScriptCore.build/Debug/JavaScriptCore.build/Objects-normal/x86_64/Heap.o In file included from /usr/include/c++/4.2.1/bits/ios_base.h:47, from /usr/include/c++/4.2.1/ios:48, from /usr/include/c++/4.2.1/ostream:45, from /usr/include/c++/4.2.1/iterator:70, from /Users/drb/devel/WebKit/WebKitBuild/Debug/usr/local/include/wtf/Deque.h:36, from
Re: [webkit-dev] build-webkit stopped working for me
On Sun, Oct 21, 2012 at 2:17 PM, Maciej Stachowiak m...@apple.com wrote: Apple did not ship the last release of Safari to SnowLeopard and we have no plans to maintain SnowLeopard support on trunk. We haven't actively ripped out SL-specific ifdefs because we were under the impression that the Chromium port still targets SL and sometimes uses Mac code paths. This is correct; Chromium still supports SL. -- Dirk ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] build-webkit stopped working for me
Thank you both for the clarification. On Sun, Oct 21, 2012 at 2:21 PM, Dirk Pranke dpra...@chromium.org wrote: On Sun, Oct 21, 2012 at 2:17 PM, Maciej Stachowiak m...@apple.com wrote: Apple did not ship the last release of Safari to SnowLeopard and we have no plans to maintain SnowLeopard support on trunk. We haven't actively ripped out SL-specific ifdefs because we were under the impression that the Chromium port still targets SL and sometimes uses Mac code paths. This is correct; Chromium still supports SL. -- Dirk ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] New CSS3 feature : text-justify
Dear WebKit, I would like to let you know that I'm trying to implement a new CSS3 feature which name is text-justify. The specification link is here : http://dev.w3.org/csswg/css3-text/#text-justify0 This property selects the justification method used when a line's alignment is set to ‘justify’ (see ‘text-align’), primarily by controlling which scripts' characters are adjusted together or separately. This feature is already properly supported on IE, currently. The bug related to this implementation is https://bugs.webkit.org/show_bug.cgi?id=99945 . Any comments will be kindly appreciated! Best regards, Dongwoo. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Client application links to JavaScriptCore instead of std lib
Hi Dipak! Add this define to your build configuration: USE_SYSTEM_MALLOC=1 Cheers, Zoltan On Sat, Oct 20, 2012 at 6:51 PM, dipak kumar mail.di...@gmail.com wrote: Hi Zoltan, Thanks a lot for your prompt reply. I am not aware where to make this change in the visual studio as I am building webkit on Windows. Could you please help me to know where to make this change. Many Thanks. Regards, Dipak On Sat, Oct 20, 2012 at 12:10 AM, Zoltan Horvath zol...@webkit.orgwrote: Hi Dipak, You should try a clean build with build-webkit --system-malloc to force WebKit to use the system's allocator. Let me know if it solves your problem. Cheers, Zoltan On Fri, Oct 19, 2012 at 5:21 AM, dipak kumar mail.di...@gmail.comwrote: Dear All, I have built Webkit (Process model) for Win32. I have developed a client application to use this webkit. My client application has a number of new/delete calls. Now when I run the client application it crashes at the location where memory is being freed. Call stack shows the crash point at free of JavaScriptCore. This free is inside fastmalloc.cpp. #if ENABLE(WTF_MALLOC_VALIDATION) if (!ptr) return; fastMallocValidate(ptr); Internal::ValidationHeader* header = Internal::fastMallocValidationHeader(ptr); memset(ptr, 0xCC, header-m_size); do_free(header); #else *do_free(ptr); - CRASH POINT* #endif Please let me know how can I stop my client application to get linked to JavaScriptCore memory functions. Awaiting reply. Many Thanks, Dipak ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
