jpeg causes gcc 4.4 segfault during build

[GoogleCodeExporter]

  CC(target) out/Debug/obj.target/libjpeg/third_party/libjpeg_turbo/jcprepct.o
  CC(target) out/Debug/obj.target/libjpeg/third_party/libjpeg_turbo/jcsample.o
third_party/libjpeg_turbo/jcprepct.c:1: internal compiler error: Segmentation 
fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.4/README.Bugs> for instructions.
  CC(target) out/Debug/obj.target/libjpeg/third_party/libjpeg_turbo/jdapimin.o
make: *** [out/Debug/obj.target/libjpeg/third_party/libjpeg_turbo/jcprepct.o] 
Error 1
make: *** Waiting for unfinished jobs....
  CC(target) out/Debug/obj.target/libjpeg/third_party/libjpeg_turbo/jdapistd.o
program finished with exit code 2
elapsedTime=154.744254

Original issue reported on code.google.com by fbarch...@google.com on 10 Sep 2012 at 9:24

[GoogleCodeExporter]

This appears to be flakey and not easily reproduced.
The jc*.* parts were previously not tested, as we only included the decoder.

Original comment by fbarch...@google.com on 11 Sep 2012 at 3:35

[GoogleCodeExporter]

webrtc and libyuv are on older versions of chromium/yasm/jpeg.
Although the bug isnt easily reproducible, it would be good to update to 
r154697 (Sept 3/2012)to pick up the yasm 1.2 update.

Original comment by fbarch...@google.com on 11 Sep 2012 at 9:59

[GoogleCodeExporter]

updates yasm and jpeg for libyuv and chromium deps in general.  fixes the build 
warning in yasm at least.

Original comment by fbarch...@chromium.org on 12 Sep 2012 at 4:25

• Changed state: Fixed