2016-12-15 20:43 GMT+01:00 Matthew Wolenetz <wolen...@chromium.org>: >> >> This seems like a rather odd issue to be toolchain specific. >> Can you please provide a configure command line that >> would result in a broken build? > > I believe the link-time failures occurred with configs like these: > > IIRC, on Mac, Chromium build hit this with: > > - > > https://cs.chromium.org/chromium/src/third_party/ffmpeg/chromium/config/Chromium/mac/x64/config.h?rcl=0&l=4 > > On Windows, one or both of the following hit this: > > - > > https://cs.chromium.org/chromium/src/third_party/ffmpeg/chromium/config/Chromium/win/ia32/config.h?rcl=0&l=4 > - > > https://cs.chromium.org/chromium/src/third_party/ffmpeg/chromium/config/Chromium/win/x64/config.h?rcl=0&l=4
These do not look like configure lines (only configure is supported)... > > DCE is needed for FFmpeg compilation, this should get fixed >> by Steve Lhomme's configure patch. >> I find it hard to understand why wavdec.c would be the only file >> showing this issue... > > Notably, windows still hit this (VS2015 Update 3 19.00.24213.1) > *even with -O2.* I believe this indicates a compiler issue that you should report upstream and for which we may not accept a workaround. Carl Eugen _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
