All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: Romain Perier <romain.perier@collabora.com>
Cc: yocto@yoctoproject.org
Subject: Re: [meta-rockchip][PATCH 4/5] u-boot-rockchip: remove duplicated variables
Date: Sat, 29 Apr 2017 02:11:00 -0400	[thread overview]
Message-ID: <20170429061100.GA7543@linux-uys3> (raw)
In-Reply-To: <20170428140126.27654-5-romain.perier@collabora.com>

This doesn't succeed for me:

	ERROR: /opt/oe/configs/z/build-master/firefly-rk3288/layers/meta-rockchip/recipes-bsp/u-boot/u-boot-rockchip_git.bb: This recipe does not have the LICENSE field set (u-boot-rockchip)
	ERROR: Failed to parse recipe: /opt/oe/configs/z/build-master/firefly-rk3288/layers/meta-rockchip/recipes-bsp/u-boot/u-boot-rockchip_git.bb

But it does work if I add...

On Fri 2017-04-28 @ 04:01:25 PM, Romain Perier wrote:
>  # Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd
>  # Copyright (C) 2017 Trevor Woerner <twoerner@gmail.com>
> +# Copyright (C) 2017 Romain Perier <romain.perier@collabora.com>
>  # Released under the MIT license (see COPYING.MIT for the terms)
>  
>  require recipes-bsp/u-boot/u-boot.inc
require recipes-bsp/u-boot/u-boot-common_2017.01.inc
>  
>  DESCRIPTION = "Rockchip next-dev U-Boot"
> -LICENSE = "GPLv2+"
> -LIC_FILES_CHKSUM = "file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6"
>  COMPATIBLE_MACHINE = "(firefly-rk3288)"
...

Does this make sense?

I'm building against openembedded-core
e584be78f92ee6f08f570c239698d56ac78d05f9

	Build Configuration:
	BB_VERSION        = "1.34.0"
	BUILD_SYS         = "x86_64-linux"
	NATIVELSBSTRING   = "opensuse-42.2"
	TARGET_SYS        = "arm-oe-linux-gnueabi"
	MACHINE           = "firefly-rk3288"
	DISTRO            = "nodistro"
	DISTRO_VERSION    = "nodistro.0"
	TUNE_FEATURES     = "arm armv7ve vfp thumb neon callconvention-hard"
	TARGET_FPU        = "hard"
	meta-rockchip     = "devs/rperier/20170429:0d89dcc4a5a2827b68d920bbd32e4aece774b5eb"
	meta              = "master:e584be78f92ee6f08f570c239698d56ac78d05f9"


  reply	other threads:[~2017-04-29  6:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-28 14:01 [meta-rockchip][PATCH 0/5] u-boot-rockchip: various improvements Romain Perier
2017-04-28 14:01 ` [meta-rockchip][PATCH 1/5] machine: add UBOOT_MACHINE definition Romain Perier
2017-04-28 14:01 ` [meta-rockchip][PATCH 2/5] u-boot-rockchip: copy spl binary from the good task Romain Perier
2017-04-28 14:01 ` [meta-rockchip][PATCH 3/5] u-boot-rockchip: use a correct version Romain Perier
2017-04-28 14:01 ` [meta-rockchip][PATCH 4/5] u-boot-rockchip: remove duplicated variables Romain Perier
2017-04-29  6:11   ` Trevor Woerner [this message]
2017-04-28 14:01 ` [meta-rockchip][PATCH 5/5] u-boot-rockchip: add rock2 to compatible machines Romain Perier

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=20170429061100.GA7543@linux-uys3 \
    --to=twoerner@gmail.com \
    --cc=romain.perier@collabora.com \
    --cc=yocto@yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.