Emerge www-client/firefox-5.0 fails with USE="-webm" Reproducible: Always This is the end of build.log: checking for YASM assembler... checking for yasm... no configure: error: yasm is required to build with libjpeg-turbo's optimized JPEG decoding routines, but you do not appear to have yasm installed. Either install it or configure with --disable-libjpeg-turbo to use the pure C JPEG decoder. See https://developer.mozilla.org/en/YASM for more details. *** Fix above errors and then restart with "make -f client.mk build" make[1]: *** [configure] Error 1 make[1]: Leaving directory `/var/calculate/tmp/portage/www-client/firefox-5.0/work/mozilla-release' make: *** [obj-i686-pc-linux-gnu/Makefile] Error 2 emake failed
Created attachment 278037 [details] build.log
Created attachment 278889 [details, diff] firefox-5.0-r1.ebuild.diff possible fix
Hum. We should be using the system jpeg, since we use libjpeg-turbo by default in the portage tree now (virtual/jpeg). Jory, should we add the yasm dep or pass --enable-system-jpeg?
(In reply to comment #3) > Hum. We should be using the system jpeg, since we use libjpeg-turbo by default > in the portage tree now (virtual/jpeg). > > Jory, should we add the yasm dep or pass --enable-system-jpeg? We should be psasing --enable-system-jpeg why we are not is beyond me.
(In reply to comment #4) > (In reply to comment #3) > > Hum. We should be using the system jpeg, since we use libjpeg-turbo by default > > in the portage tree now (virtual/jpeg). > > > > Jory, should we add the yasm dep or pass --enable-system-jpeg? > > We should be psasing --enable-system-jpeg why we are not is beyond me. Probably because Firefox isn't ported to jpeg-turbo-1.2 yet[1], and jpeg-turbo-1.2 is ~arch in portage. 1. https://bugzilla.mozilla.org/show_bug.cgi?id=698519
(In reply to comment #5) > (In reply to comment #4) > > (In reply to comment #3) > > > Hum. We should be using the system jpeg, since we use libjpeg-turbo by default > > > in the portage tree now (virtual/jpeg). > > > > > > Jory, should we add the yasm dep or pass --enable-system-jpeg? > > > > We should be psasing --enable-system-jpeg why we are not is beyond me. > > Probably because Firefox isn't ported to jpeg-turbo-1.2 yet[1], and > jpeg-turbo-1.2 is ~arch in portage. > > 1. https://bugzilla.mozilla.org/show_bug.cgi?id=698519 Actually this is a mute point, refer to mozcoreconf-2.eclass and you will see --enable-system-jpeg is already passed.
Ah yes, closing then.
