diff options
| author | Ross Burton <ross.burton@arm.com> | 2025-09-24 13:07:35 +0100 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2025-09-25 11:09:04 +0100 |
| commit | 917d6652fc1c0610fd493990395b6b528613879d (patch) | |
| tree | c7aabc4af5710783e8113e3dcf92ec75148e5662 /scripts/lib/build_perf/report.py | |
| parent | 0068ff98105a8128a4cc1d1f4d33d195a23dcb50 (diff) | |
| download | poky-917d6652fc1c0610fd493990395b6b528613879d.tar.gz | |
lame: don't use -march=native when building with clang
Because of a logic error, lame's configure always passes -march=native
when building with clang.
This is a terrible idea in general as it's not often your build machine
and target hardware aligns, and leads to some amusing errors:
unknown target CPU 'neoverse-n1'
note: valid target CPU values are: i386, i486, ...
Move the HAVE_CLANG block up into the FULL_OPTIMIZATION case, alongside
HAVE_GCC. This option is never enabled (as it's basically "use native")
so resolves the build failure.
(From OE-Core rev: d6f0e26ccf19872e1f4eebb346d76c7bff87ba2a)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts/lib/build_perf/report.py')
0 files changed, 0 insertions, 0 deletions