diff options
| author | Markus Volk <f_l_k@t-online.de> | 2022-12-03 08:43:24 +0100 |
|---|---|---|
| committer | Armin Kuster <akuster808@gmail.com> | 2023-01-23 10:15:10 -0500 |
| commit | 84ba7671136d02a7d86b23be49bf8a57ac42d378 (patch) | |
| tree | d4a2d85e82d74dc3857bc4fa460a607795e6f1cd /meta-python/recipes-devtools/python/python3-pyfanotify/0001-ext-define-FNM_EXTMATCH-if-not-already-defined.patch | |
| parent | f9ea77c5ab4c922da97e19fc34d4af18ff5ba1a1 (diff) | |
| download | meta-openembedded-84ba7671136d02a7d86b23be49bf8a57ac42d378.tar.gz | |
perfetto: pass TUNE_CCARGS to use machine tune
We already tried to pass -mfloat-abi=hard if the machine can use it, but since
no floating-point-unit was defined it got stubbed out and the result was, that
only arm targets configured for softfp were able to build perfetto.
Simplify by passing ${TUNE_CCARGS} to ensure, we always use the features, the
machine was configured for.
Also, do not use sed to remove the hardcoded -mfpu=neon entry. If this really
turns out to be problematic, we need to patch it out to avoid not having a
floating-point-unit again.
Signed-off-by: Markus Volk <f_l_k@t-online.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit c23bde86d0bcba3acc677bc4cd3240a8b3116921)
[Fixes build failure]
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Diffstat (limited to 'meta-python/recipes-devtools/python/python3-pyfanotify/0001-ext-define-FNM_EXTMATCH-if-not-already-defined.patch')
0 files changed, 0 insertions, 0 deletions