Bug 18236 - Build failure in JavaScriptCore/kjs/
Summary: Build failure in JavaScriptCore/kjs/
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Linux
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-31 10:17 PDT by Fryderyk Dziarmagowski
Modified: 2008-05-18 09:45 PDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fryderyk Dziarmagowski 2008-03-31 10:17:42 PDT
Building latest nightly snapshot fails with:

/bin/sh ./libtool --tag=CXX   --mode=compile i686-mipld-linux-g++ -DHAVE_CONFIG_H -I.  -DWTF_USE_ICU_UNICODE=1 -DBUILDING_GTK__=1 -DWTF_CHANGES  -DXP_UNIX -DNDEBUG  -DENABLE_ICONDATABASE=0  -I./JavaScriptCore -I./JavaScriptCore/ForwardingHeaders -I./JavaScriptCore/wtf -I./JavaScriptCore/kjs -I./DerivedSources -I./JavaScriptCore/ForwardingHeaders -I./JavaScriptCore/wtf/unicode -I./JavaScriptCore/pcre -I./JavaScriptCore/kjs   -fno-rtti -Wall -W -Wcast-align -Wchar-subscripts -Wreturn-type -Wformat -Wformat-security -Wno-format-y2k -Wundef -Wmissing-format-attribute -Wpointer-arith -Wwrite-strings -Wno-unused-parameter -fno-exceptions  -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include   -D_REENTRANT -D_REENTRANT -I/usr/include -fstrict-aliasing -O2 -fno-strict-aliasing -fwrapv -march=i686 -mtune=pentium4 -gdwarf-2 -g2  -MT JavaScriptCore/kjs/libJavaScriptCore_la-AllInOneFile.lo -MD -MP -MF JavaScriptCore/kjs/.deps/libJavaScriptCore_la-AllInOneFile.Tpo -c -o JavaScriptCore/kjs/libJavaScriptCore_la-AllInOneFile.lo `test -f 'JavaScriptCore/kjs/AllInOneFile.cpp' || echo './'`JavaScriptCore/kjs/AllInOneFile.cpp
 i686-mipld-linux-g++ -DHAVE_CONFIG_H -I. -DWTF_USE_ICU_UNICODE=1 -DBUILDING_GTK__=1 -DWTF_CHANGES -DXP_UNIX -DNDEBUG -DENABLE_ICONDATABASE=0 -I./JavaScriptCore -I./JavaScriptCore/ForwardingHeaders -I./JavaScriptCore/wtf -I./JavaScriptCore/kjs -I./DerivedSources -I./JavaScriptCore/ForwardingHeaders -I./JavaScriptCore/wtf/unicode -I./JavaScriptCore/pcre -I./JavaScriptCore/kjs -fno-rtti -Wall -W -Wcast-align -Wchar-subscripts -Wreturn-type -Wformat -Wformat-security -Wno-format-y2k -Wundef -Wmissing-format-attribute -Wpointer-arith -Wwrite-strings -Wno-unused-parameter -fno-exceptions -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -D_REENTRANT -D_REENTRANT -I/usr/include -fstrict-aliasing -O2 -fno-strict-aliasing -fwrapv -march=i686 -mtune=pentium4 -gdwarf-2 -g2 -MT JavaScriptCore/kjs/libJavaScriptCore_la-AllInOneFile.lo -MD -MP -MF JavaScriptCore/kjs/.deps/libJavaScriptCore_la-AllInOneFile.Tpo -c JavaScriptCore/kjs/AllInOneFile.cpp  -fPIC -DPIC -o JavaScriptCore/kjs/.libs/libJavaScriptCore_la-AllInOneFile.o
In file included from JavaScriptCore/kjs/AllInOneFile.cpp:55:
JavaScriptCore/kjs/nodes.h:211: error: `typedef enum KJS::ExpressionNode::CallerType KJS::ExpressionNode::CallerType' is protected
JavaScriptCore/kjs/nodes.cpp:1090: error: within this context
make[1]: *** [JavaScriptCore/kjs/libJavaScriptCore_la-AllInOneFile.lo] Error 1

Build enviroment:
r31446
gcc 3.4.6
glibc 2.5
default configure options
Comment 1 Serbulent 2008-04-06 00:59:58 PDT
I have the same bug with r31667 and r31623 . 

using command ./build-webkit --gtk --qmake=qmake-qt4
also ./build-webkit --qmake=qmake-qt4 gives same result. My system info is below 
if u need more please tell me.

Linux 2.6.18-86
gcc 3.4.6
QMake version 2.01a
Using Qt version 4.3.4
glibc 2.3.6
gtk-engines  2.11.2 
gtk-qt-engine  0.8
gtk2      2.12.8
Comment 2 Alexey Proskuryakov 2008-04-07 00:20:12 PDT
This just looks like a gcc bug to me. Do we even attempt to support anything below gcc 4? Is there a reason to support older versions?
Comment 3 Georgi Kirilov 2008-05-06 02:51:13 PDT
There are embedded devices for which the toolchain is supplied by the hardware vendor, and they do not support the newest gcc versions. A while ago I built WebKitGtk for a mipsel device and many problems arose because of the old toolchain/libraries (mainly uClibc). The vendor just said they don't have the time to support newer versions. So if a workaround for a not too old gcc is possible (and is not too complicated) I think it is worth.
Comment 4 Fryderyk Dziarmagowski 2008-05-18 09:45:37 PDT
seem to be fixed in r33561! closing as FIXED.