diff options
| author | Masahiro Yamada <[email protected]> | 2021-06-10 11:03:31 +0900 |
|---|---|---|
| committer | Helge Deller <[email protected]> | 2021-09-01 21:52:02 +0200 |
| commit | 5f6e0fe01b6b33894cf6f61b359ab5a6d2b7674e (patch) | |
| tree | 8014d290820ba2a04d7f2f6a7d32a86061e3d908 /tools/perf/scripts/python/Perf-Trace-Util/lib/Perf | |
| parent | 8ef5b28d670b76601e14476b00a505854abc838b (diff) | |
parisc: Fix compile failure when building 64-bit kernel natively
Commit 23243c1ace9f ("arch: use cross_compiling to check whether it is
a cross build or not") broke 64-bit parisc builds on 32-bit parisc
systems.
Helge mentioned:
- 64-bit parisc userspace is not supported yet [1]
- hppa gcc does not support "-m64" flag [2]
That means, parisc developers working on a 32-bit parisc machine need
to use hppa64-linux-gnu-gcc (cross compiler) for building the 64-bit
parisc kernel.
After the offending commit, gcc is used in such a case because
both $(SRCARCH) and $(SUBARCH) are 'parisc', hence cross_compiling is
unset.
A correct way is to introduce ARCH=parisc64 because building the 64-bit
parisc kernel on a 32-bit parisc system is not exactly a native build,
but rather a semi-cross build.
[1]: https://lore.kernel.org/linux-parisc/[email protected]/#t
[2]: https://lore.kernel.org/linux-parisc/[email protected]/
Fixes: 23243c1ace9f ("arch: use cross_compiling to check whether it is a cross build or not")
Signed-off-by: Masahiro Yamada <[email protected]>
Reported-by: Meelis Roos <[email protected]>
Tested-by: Meelis Roos <[email protected]>
Cc: <[email protected]> # v5.13+
Signed-off-by: Helge Deller <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/Perf-Trace-Util/lib/Perf')
0 files changed, 0 insertions, 0 deletions