From: Baruch Siach <baruch@tkos.co.il>
To: Patricia Holden <pholden@nklabs.com>
Cc: buildroot@busybox.net, Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] Question about pkg-config pc files
Date: Fri, 23 Jul 2021 06:39:26 +0300 [thread overview]
Message-ID: <87a6mdzok1.fsf@tarshish> (raw)
In-Reply-To: <CAJ6EmCfnhev8MLO7JNx3d8trX7uEn+DgkdWZHKguyW8kG92ZhQ@mail.gmail.com>
Hi Patricia,
On Fri, Jul 23 2021, Patricia Holden wrote:
> I switched from ti-gfx to ti-sgx, now I get another error:
>
> /home/patricaholden/williamson/build07062021/Pro3-Linux/buildroot-2020.02/output/build/ti-sgx-km-4519ed3b83d1d72207ddc2874c7eb5e5a7f20d8d/eurasia_km/eurasiacon/binary_omap_linux_xorg_release/target_armhf/kbuild/services4/srvkm/env/linux/mm.c:69:10:
> fatal error: linux/dma-direct.h: No such file or directory
> 69 | #include <linux/dma-direct.h>
> | ^~~~~~~~~~~~~~~~~~~~
>
>
> I checked linux-headers and only see "include/linux/dma-direction.h", no
> "include/linux/dma-direct.h".
The linux-headers package is for userspace API (uapi) headers that are
part of the toolchain. dma-direction.h is for kernel code. The 'kbuild'
part in the path above indicates that you are building a kernel module.
linux/dma-direct.h was introduced in kernel version 4.16 (commit
ea8c64ace866). But ti-sgx-km commit cf7f48cb30a predates this kernel by
few years. So this it probably a TI kernel that carries the header.
The BR2_PACKAGE_TI_SGX_KM help text says this:
Note: it needs a TI specific kernel to build properly.
baruch
> Not sure if this is the same file this package is looking for, but just
> renamed. Looking through config for the kernel to see if I missed
> something.
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-07-23 3:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 20:41 [Buildroot] Question about pkg-config pc files Patricia Holden
2021-07-20 20:41 ` Patricia Holden
2021-07-20 20:48 ` Thomas Petazzoni
2021-07-20 20:48 ` Thomas Petazzoni
2021-07-21 6:23 ` Patricia Holden
2021-07-21 7:41 ` Thomas Petazzoni
2021-07-21 19:07 ` Patricia Holden
2021-07-21 22:53 ` Patricia Holden
2021-07-22 17:36 ` Patricia Holden
2021-07-22 19:40 ` Arnout Vandecappelle
2021-07-22 19:52 ` Patricia Holden
2021-07-22 23:38 ` Patricia Holden
2021-07-23 3:39 ` Baruch Siach [this message]
2021-07-23 18:52 ` Patricia Holden
2021-07-23 20:57 ` Arnout Vandecappelle
2021-07-23 22:21 ` Patricia Holden
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a6mdzok1.fsf@tarshish \
--to=baruch@tkos.co.il \
--cc=buildroot@busybox.net \
--cc=pholden@nklabs.com \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox