Re: Compilation error in Xulrunner code

Hi Neil,

Thank you very much for your reply.
It requires some library dependency and some options in .mozconf file we have to modify for the requirement.

Now xulrunner 1.9 source code compiling fine in ubuntu without any error. 
but one more question. Below is my configuration file.

mk_add_options MOZ_CO_PROJECT=xulrunner
mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/obj-xul-lin-dbg
mk_add_options MOZ_MAKE_FLAGS="-s -j4"

ac_add_options --disable-tests
ac_add_options --enable-logging
ac_add_options --enable-debug
ac_add_options --disable-optimize
ac_add_options --disable-crashreporter
ac_add_options --disable-installer
ac_add_options --enable-application=xulrunner
ac_add_options --enable-jemalloc
ac_add_options --disable-gstreamer
ac_add_options --with-java-bin-path=/usr/lib/jvm/java-6-openjdk/bin
#ac_add_options --disable-ogg
#ac_add_options --disable-wave
ac_add_options --disable-javaxpcom


After successful build we have executed "install" command to install the binary.

Where it will install ? what is the location for the binary and library files which we install ?

Thanks in Advance

On Friday, December 6, 2013 12:47:53 PM UTC+5:30, [email protected] wrote:
> Hi All,
> 
> 
> 
> We have downloaded the code of mozilla xulrunner 1.9 and compiling the source code.
> 
> 
> 
> As we are getting the below error.
> 
> 
> 
> nsSVGStylableElement.cpp
> 
> nsSVGRect.cpp
> 
> nsSVGRectElement.cpp
> 
> nsSVGSVGElement.cpp
> 
> nsSVGStopElement.cpp
> 
> nsSVGStyleElement.cpp
> 
> nsSVGSwitchElement.cpp
> 
> nsSVGSymbolElement.cpp
> 
> nsSVGTSpanElement.cpp
> 
> nsSVGTextContentElement.cpp
> 
> nsSVGTextElement.cpp
> 
> nsSVGTextPathElement.cpp
> 
> nsSVGTitleElement.cpp
> 
> nsSVGTransform.cpp
> 
> nsSVGTransformList.cpp
> 
> nsSVGTransformListParser.cpp
> 
> nsSVGUseElement.cpp
> 
> nsSVGValue.cpp
> 
> nsSVGViewBox.cpp
> 
> make[3]: *** [libs_tier_gecko] Error 2
> 
> make[2]: *** [tier_gecko] Error 2
> 
> make[1]: *** [default] Error 2
> 
> make: *** [build] Error 2
> 
> 
> 
> 
> 
> 
> 
> Can anyone tell me where is the error ? Because we are not able to figure out where is the error ?
> 
> 
> 
> Thanks in Advance.