Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Joshua Watt <jpewhacker@gmail.com>
To: OE-core <openembedded-core@lists.openembedded.org>
Cc: Marek Vasut <marex@denx.de>, Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [PATCH v2] u-boot: Fix pylibfdt generation
Date: Thu, 02 Aug 2018 12:25:57 -0500	[thread overview]
Message-ID: <f6ed4f2afd6d43944565fcffa8bc90625770ea50.camel@gmail.com> (raw)
In-Reply-To: <20180731171913.5202-1-JPEWhacker@gmail.com>

On Tue, 2018-07-31 at 12:19 -0500, Joshua Watt wrote:
> u-boot attempts to build a Python library called pylibfdt. By
> default,
> u-boot would attempt to use the build host's Python interpreter,
> which
> causes numerous problems, not least of which is that it fails if the
> host doesn't have the Python development package installed
> (complaining
> about not being able to find Python.h)
> 
> Rectify this situation by including the proper build time
> dependencies
> for pylibfdt and passing the proper arguments to make.
> 
> [YOCTO #12867]
> 
> Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
> ---
>  meta/recipes-bsp/u-boot/u-boot.inc | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/meta/recipes-bsp/u-boot/u-boot.inc b/meta/recipes-bsp/u-
> boot/u-boot.inc
> index c2bcf998402..95c2f4db14d 100644
> --- a/meta/recipes-bsp/u-boot/u-boot.inc
> +++ b/meta/recipes-bsp/u-boot/u-boot.inc
> @@ -7,8 +7,11 @@ PACKAGE_ARCH = "${MACHINE_ARCH}"
>  
>  inherit uboot-config uboot-extlinux-config uboot-sign deploy
>  
> +DEPENDS += "swig-native python-native"
> +
>  EXTRA_OEMAKE = 'CROSS_COMPILE=${TARGET_PREFIX}
> CC="${TARGET_PREFIX}gcc ${TOOLCHAIN_OPTIONS}" V=1'
>  EXTRA_OEMAKE += 'HOSTCC="${BUILD_CC} ${BUILD_CFLAGS}
> ${BUILD_LDFLAGS}"'
> +EXTRA_OEMAKE += 'PYTHON=nativepython
> STAGING_INCDIR=${STAGING_INCDIR_NATIVE}
> STAGING_LIBDIR=${STAGING_LIBDIR_NATIVE}'
>  
>  PACKAGECONFIG ??= "openssl"
>  # u-boot will compile its own tools during the build, with specific

This was applied to master as 581a2cb7f8dfc88af785d55ef5ce40b0939c465b.

Armin, could you please backport to sumo?

Thanks,
-- 
Joshua Watt <JPEWhacker@gmail.com>


  reply	other threads:[~2018-08-02 17:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-19 16:31 [PATCH] u-boot: Fix pylibfdt generation Joshua Watt
2018-07-19 20:10 ` Burton, Ross
2018-07-19 21:36   ` Joshua Watt
2018-07-31 17:19 ` [PATCH v2] " Joshua Watt
2018-08-02 17:25   ` Joshua Watt [this message]
2018-08-02 18:40     ` akuster808

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=f6ed4f2afd6d43944565fcffa8bc90625770ea50.camel@gmail.com \
    --to=jpewhacker@gmail.com \
    --cc=marex@denx.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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