diff options
| author | Christian Lamparter <chunkeey@gmail.com> | 2022-09-24 19:57:26 +0200 |
|---|---|---|
| committer | Christian Lamparter <chunkeey@gmail.com> | 2022-09-24 23:52:14 +0200 |
| commit | 1ce2691bf3dacca41559a20e7f1a55587469dfae (patch) | |
| tree | 2675e48905b479e277ea8a0be99e58c97c08b632 /target/linux/realtek/patches-5.10/319-irqchip-irq-realtek-rtl-fix-VPE-affinity.patch | |
| parent | b02b95d1b0816274e5cf221071e0f52482c7537a (diff) | |
| download | upstream-1ce2691bf3dacca41559a20e7f1a55587469dfae.tar.gz upstream-1ce2691bf3dacca41559a20e7f1a55587469dfae.tar.bz2 upstream-1ce2691bf3dacca41559a20e7f1a55587469dfae.zip | |
uml: headers are not exportable
When building UML this showed up as of late (2022-09-01):
| Makefile:1335: *** Headers not exportable for UML. Stop.
This message popped up because of an upstream patch that
fixed this error not showing up sooner. For more information see:
<https://lore.kernel.org/lkml/20220901011252.550830-1-masahiroy@kernel.org/T/>
Now, I don't think we can just skip the kernel headers.
Some userspace applications are going to need these. So,
The next best alternative I can think of, is to go with
the headers by the host arch the UML is compiled for.
(Technically, ARCH= should be safe for all other targets
as well... But let's not poke a hornet's nest)
Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
Diffstat (limited to 'target/linux/realtek/patches-5.10/319-irqchip-irq-realtek-rtl-fix-VPE-affinity.patch')
0 files changed, 0 insertions, 0 deletions