2d9f199061
m68k coldfire causes ffmpeg to think atomic intrinsics are available, so ffmpeg doesn't use its fallback on pthreads based atomic operations. However, m68k coldfire doesn't provide properly working sync 4 atomics, causing a build failure. Since fixing ffmpeg on m68k coldfire is not really important (who wants to use ffmpeg on such platform?), we simply disallow the selection of ffmpeg on this platform. Alternate approaches have been proposed in the past: - Bernd Kuhls proposed in http://patchwork.ozlabs.org/patch/766909/ to add a dependency on BR2_TOOLCHAIN_HAS_SYNC_4, but this is wrong because other architectures that lack sync 4 atomics, such as Sparc, can build ffmpeg perfectly fine thanks to the pthreads based fallback code. - Waldemar Brodkorb proposed in https://patchwork.ozlabs.org/patch/756664/ to add an explicit option in ffmpeg configure to force the use of pthreads based atomics. However, we believe that running ffmpeg on m68k coldfire is such an unlikely use case that it isn't worth carrying a patch for this. Fixes: http://autobuild.buildroot.net/results/b3e/b3eaaf6d73cd49f5919143aeaa5cbb4d15a7ccc3/ Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> |
||
|---|---|---|
| arch | ||
| board | ||
| boot | ||
| configs | ||
| docs | ||
| fs | ||
| linux | ||
| package | ||
| support | ||
| system | ||
| toolchain | ||
| .defconfig | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitlab-ci.yml.in | ||
| CHANGES | ||
| Config.in | ||
| Config.in.legacy | ||
| COPYING | ||
| DEVELOPERS | ||
| Makefile | ||
| Makefile.legacy | ||
| README | ||
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. The documentation can be found in docs/manual. You can generate a text document with 'make manual-text' and read output/docs/manual/manual.text. Online documentation can be found at http://buildroot.org/docs.html To build and use the buildroot stuff, do the following: 1) run 'make menuconfig' 2) select the target architecture and the packages you wish to compile 3) run 'make' 4) wait while it compiles 5) find the kernel, bootloader, root filesystem, etc. in output/images You do not need to be root to build or run buildroot. Have fun! Buildroot comes with a basic configuration for a number of boards. Run 'make list-defconfigs' to view the list of provided configurations. Please feed suggestions, bug reports, insults, and bribes back to the buildroot mailing list: buildroot@buildroot.org You can also find us on #buildroot on Freenode IRC. If you would like to contribute patches, please read https://buildroot.org/manual.html#submitting-patches