From: Juergen Borleis <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: "Alejandro Vázquez" <vazlup@gmail.com>
Subject: Re: [ptxdist] kernel headers in ptxdist
Date: Tue, 31 Jan 2017 10:49:51 +0100 [thread overview]
Message-ID: <201701311049.51452.jbe@pengutronix.de> (raw)
In-Reply-To: <CAEt18EX7p1EENcgs+jKQcse9LAubDO-oRSbx=e2R20BZQcih2g@mail.gmail.com>
Hi Alejandro,
On Tuesday 31 January 2017 10:27:04 Alejandro Vázquez wrote:
> I need use kernel headers to build a IPU app.
> I select KERNEL_HEADERS in ptxdist and I add
> CFLAGS="-I$(KERNEL_HEADERS_INCLUDE_DIR)" in *.make.
> Also I have added in the makefile -I$(KERNEL_HEADERS_INCLUDE_DIR)
>
> But it still does not compile because it does not find the headers.
> It looks like the variable KERNEL_HEADERS_INCLUDE_DIR is empty, this can
> be seen in the output of the compilation.
>
> -------------------------
> > target: alpha_ex1.compile
> > -------------------------
> > make[1]: Entering directory `/ptxdist/BSP/local_src/alpha_ex1'
> > arm-v7a-linux-gnueabihf-gcc -g -O0 -o alpha_ex1 alpha_ex1.c -I \
> > -I/uapi
> > alpha_ex1.c:26:25: fatal error: linux/mxcfb.h: No such file or
> > directory #include <linux/mxcfb.h>
>
> Is there something wrong?
Yes. You modify CFLAGS but you do not use it in your local Makefile.
Try this instead:
[...]
ALPHA_EX1_MAKE_ENV := $(CROSS_ENV) \
"KERNEL_HEADERS_INCLUDE_DIR=$(KERNEL_HEADERS_INCLUDE_DIR)"
[...]
This should set and forward the variable to 'make' when it works through
your local Makefile.
Happy hacking
Juergen
--
Pengutronix e.K. | Juergen Borleis |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-01-31 9:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 9:27 Alejandro Vázquez
2017-01-31 9:49 ` Juergen Borleis [this message]
2017-01-31 10:36 ` Alejandro Vázquez
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=201701311049.51452.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=vazlup@gmail.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