Fix non-neon ARM builds of libaom

Linking fails when building chromium for non-NEON ARM w/ the following:

ld.lld: error: undefined symbol: aom_arm_cpu_caps
>>> referenced by av1_rtcd.h:1055 (../../third_party/libaom/source/config/linux/arm/config/av1_rtcd.h:1055)
>>>               libaom/av1_rtcd.o:(.text+0x0) in archive obj/third_party/libaom/libaom.a
>>> referenced by aom_dsp_rtcd.h:3476 (../../third_party/libaom/source/config/linux/arm/config/aom_dsp_rtcd.h:3476)
>>>               libaom/aom_dsp_rtcd.o:(.text+0x0) in archive obj/third_party/libaom/libaom.a
>>> referenced by aom_scale_rtcd.h:162 (../../third_party/libaom/source/config/linux/arm/config/aom_scale_rtcd.h:162)
>>>               libaom/aom_scale_rtcd.o:(.text+0x0) in archive obj/third_party/libaom/libaom.a

The function aom_arm_cpu_caps() in third_party/libaom is used inside
of several libaom header files, and is used by all arm boards to
actually determine the running CPU capabilities. As such,
arm_cpudetect.c needs to be included in sources for all arm boards,
not just ones that support NEON.


The full build log for the original failure can be seen here:
https://buildd.debian.org/status/fetch.php?pkg=chromium&arch=armhf&ver=99.0.4818.0-0.1&stamp=1642756579&raw=0

Debian is now using this patch, which succeeds and allows libaom to
be built properly for both our arm64 and armhf architectures:
https://buildd.debian.org/status/fetch.php?pkg=chromium&arch=arm64&ver=106.0.5249.61-1&stamp=1664422573&raw=0
https://buildd.debian.org/status/fetch.php?pkg=chromium&arch=armhf&ver=106.0.5249.61-1&stamp=1664355966&raw=0


R=jzern@chromium.org

Change-Id: I08e6ddbaf43d7de6575720911fa073ec1b7c8303
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3926048
Reviewed-by: James Zern <jzern@google.com>
Commit-Queue: James Zern <jzern@google.com>
Auto-Submit: Andres Salomon <dilinger@queued.net>
Cr-Commit-Position: refs/heads/main@{#1053334}
1 file changed
tree: db4926117fb0f65b1435b9abf10e408a4f93df73
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. AUTHORS
  63. BUILD.gn
  64. CODE_OF_CONDUCT.md
  65. codereview.settings
  66. DEPS
  67. DIR_METADATA
  68. ENG_REVIEW_OWNERS
  69. LICENSE
  70. LICENSE.chromium_os
  71. OWNERS
  72. PRESUBMIT.py
  73. PRESUBMIT_test.py
  74. PRESUBMIT_test_mocks.py
  75. README.md
  76. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure .

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.