Ideally if Unit A is disabled but another Unit B is enabled & it depends on 
Unit A, the configure should fail listing the reason. However, as what you are 
saying this is not happening.

I will try to find a workaround. Thanks for the help
On Friday, 19 September 2014 04:05:24 UTC-7, Ted Mielczarek  wrote:
> On 9/18/2014 6:25 PM, sheeri185adi...@gmail.com wrote:
> 
> > Hi,
> 
> >
> 
> > I am trying to build Firefox with our custom toolchain on host linux box.
> 
> > My mozconfig file is :
> 
> > mk_add_options MOZ_OBJDIR=/home/mk7/firefox/obj-dir
> 
> > ac_add_options --enable-application=browser
> 
> > ac_add_options --enable-optimize
> 
> > ac_add_options --disable-tests
> 
> > ac_add_options --disable-crypto
> 
> > ac_add_options --prefix=/home/mk7/firefox/install
> 
> > ac_add_options --disable-gio
> 
> > ac_add_options --disable-gconf
> 
> > ac_add_options --disable-dbus
> 
> > ac_add_options --disable-websms-backend
> 
> > ac_add_options --disable-jsd
> 
> > ac_add_options --disable-dbm
> 
> > ac_add_options --disable-webspeech
> 
> > ac_add_options --disable-webrtc
> 
> > ac_add_options --disable-opus
> 
> > ac_add_options --disable-pulseaudio
> 
> > ac_add_options --disable-gstreamer
> 
> > ac_add_options --disable-webm
> 
> > ac_add_options --disable-necko-wifi
> 
> >
> 
> > when I run the command "make -f client.mk"
> 
> >
> 
> > I get the following error and compilation stops :
> 
> >
> 
> > In file included from 
> > /home/mk7/firefox/mozilla-release/media/libmkv/EbmlBufferWriter.c:3:0:
> 
> > /home/mk7/firefox/mozilla-release/media/libmkv/EbmlWriter.h:18:29: fatal 
> > error: vpx/vpx_integer.h: No such file or directory
> 
> >  #include "vpx/vpx_integer.h"
> 
> >                              ^
> 
> > compilation terminated.
> 
> >
> 
> >
> 
> > Can you help to resolve this ?
> 
> >
> 
> Generally the more configure options you use the better chance of
> 
> something breaking. I understand that when porting to a new platform or
> 
> using an odd toolchain it helps to reduce the surface area, but these
> 
> options are not well-tested. In this case, it looks like the combination
> 
> of --disable-webrtc and --disable-webm is breaking your build, because
> 
> the libmkv code relies on the libvpx code being built, but the latter is
> 
> not built when both of those options are specified. You can file a bug
> 
> on this in the Core: Build Config component and we can get it fixed, but
> 
> until that point your easiest workaround would probably be to remove
> 
> --disable-webm from your mozconfig.
> 
> 
> 
> -Ted

_______________________________________________
dev-builds mailing list
dev-builds@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-builds

Reply via email to