From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Sourabh Hegde <hrsourabh011@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] Error linking against target architecture while building new package
Date: Thu, 14 Sep 2023 21:47:33 +0200 [thread overview]
Message-ID: <20230914214733.5db06617@windsurf> (raw)
In-Reply-To: <CADYjeSuUpRDgDQt4PWKFF-gVxWBmb=xB4Aa_FrMsVyvbFzWnqg@mail.gmail.com>
On Thu, 14 Sep 2023 17:25:37 +0200
Sourabh Hegde <hrsourabh011@gmail.com> wrote:
> vsi_nn_daemon.c:25:10: fatal error: vsi_nn_daemon.h: No such file or
> directory
> 25 | #include "vsi_nn_daemon.h"
> | ^~~~~~~~~~~~~~~~~
> compilation terminated.
> make[4]: ***
> [/.../build/imx-nn-accelerator-lf-5.15.71-2.2.1/common.target:101:
> bin_r/vsi_nn_daemon.o] Error 1
> make[4]: *** Waiting for unfinished jobs....
> vsi_nn_ops.c:25:10: fatal error: vsi_nn_ops.h: No such file or directory
> 25 | #include "vsi_nn_ops.h"
> | ^~~~~~~~~~~~~~
> compilation terminated.
> make[4]: ***
> [/.../build/imx-nn-accelerator-lf-5.15.71-2.2.1/common.target:101:
> bin_r/vsi_nn_ops.o] Error 1
> vsi_nn_node_attr_template.c:26:10: fatal error: vsi_nn_node.h: No such file
> or directory
> 26 | #include "vsi_nn_node.h"
> | ^~~~~~~~~~~~~~~
> compilation terminated.
>
> However, "vsi_nn_daemon." header file is available in
> /build/imx-nn-accelerator-lf-5.15.71-2.2.1/include/OVXLIB/vsi_nn_daemon.h
> and
> /build/imx-nn-accelerator-lf-5.15.71-2.2.1/ovxlib/include/vsi_nn_daemon.h
> Also as you can see in above log, LDFLAGS=""...
If those headers are part of the imx-nn-accelerator code, it probably
means that the fact we're passing CFLAGS="..." overrides some CFLAGS
defined by the package Makefile, while it should append to the CFLAGS
passed in the environment. Sometimes it requires tweaking the Makefile
of the package, sometimes it means CFLAGS need to be passed in the
environment of make (by Buildroot) instead of as argument:
$(TARGET_MAKE_ENV) \
$(TARGET_CONFIGURE_OPTS) \
...
$(MAKE) -C $(@D)
This really requires a package-specific investigation.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-09-14 19:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 10:15 [Buildroot] Error linking against target architecture while building new package Sourabh Hegde
2023-09-14 13:14 ` Thomas Petazzoni via buildroot
2023-09-14 15:25 ` Sourabh Hegde
2023-09-14 19:47 ` Thomas Petazzoni via buildroot [this message]
2023-09-14 21:11 ` Sourabh Hegde
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=20230914214733.5db06617@windsurf \
--to=buildroot@buildroot.org \
--cc=hrsourabh011@gmail.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