Re: [webkit-dev] build-webkit stopped working for me

2012-10-22 Thread Dave Barton
Thanks very much to all three of you!

FYI, building with --chromium still compiles ok on Snow Leopard, though it 
takes longer than just building plain WebKit. It uses clang instead of gcc.

Take care, Dave B.

On Oct 21, 2012, at 4:54 PM, Eric Seidel wrote:

 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


Re: [webkit-dev] build-webkit stopped working for me

2012-10-21 Thread Maciej Stachowiak

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

2012-10-21 Thread Dirk Pranke
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

2012-10-21 Thread Eric Seidel
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