> > 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 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.* On Thu, Dec 15, 2016 at 1:06 AM, Carl Eugen Hoyos <ceffm...@gmail.com> wrote: > 2016-12-15 0:31 GMT+01:00 Matthew Wolenetz <wolen...@chromium.org>: > > Some toolchains failed to link a dynamic library containing wavdec.c, > > but with either CONFIG_SPDIF_DEMUXER or CONFIG_W64_DEMUXER disabled. > > 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... > > Carl Eugen > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel > _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
