All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: Eddie Cai <eddie.cai.linux@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [meta-rockchip][PATCH v2 2/5] u-boot-rockchip: add
Date: Tue, 21 Feb 2017 17:18:12 -0500	[thread overview]
Message-ID: <CAHUNapSvaH+a2=J09Nx6ff5Kt1LWxf4qtQs6B10YLG+CvOdV6w@mail.gmail.com> (raw)
In-Reply-To: <CAHUNapQM6ABxtp+5xy_0YjHUiy8F6VqVCK_9hcQPcxQaWeQq3A@mail.gmail.com>

I can't reproduce the problem you're seeing and I'm interested in
knowing more about how you're building to see if I can reproduce it.

I've done 4 builds: 2 on master, 2 on morty; one of which (for each
master and morty) is poky and one on OE's nodistro. All of them are
able to build this recipe (as I've contributed it) whether or not it's
the first time, or it's in sstate, after a clean, on a fresh build...
That's why I "fixed" this line, because with the previous line it
always failed once and then work the second time the build was run.

Maybe you could post the build configuration from your build? That way
I could see what layers you're enabling and at what revisions? Mine
is:

meta-rockchip     =
devs/twoerner/feb-updates-2:c252843cf2bf8326ccf2b552b59209f7a2ac3f16
meta              = master:def3800c7e58d9d1b54ea1df27b190a0f6d1d544

On Tue, Feb 21, 2017 at 11:01 AM, Trevor Woerner <twoerner@gmail.com> wrote:
> I'll have to investigate this further. From a completely clean build
> do_install_prepend always fails the first time, but simply restarting
> the build again causes it to succeed. With do_deploy_prepend it always
> succeeds without issue whether its the first or subsequent tries.
>
> On Mon, Feb 20, 2017 at 6:14 AM, Eddie Cai <eddie.cai.linux@gmail.com> wrote:
>>
>>
>> 2017-02-19 22:33 GMT+08:00 Eddie Cai <eddie.cai.linux@gmail.com>:
>>>
>>>
>>>
>>> 2017-02-19 22:22 GMT+08:00 Jacob Chen <jacobchen110@gmail.com>:
>>>>
>>>> Hi,
>>>>
>>>> 2017-02-19 10:43 GMT+08:00 Trevor Woerner <twoerner@gmail.com>:
>>>> > This recipe was taken from the Rockchip team's recipe at
>>>> >
>>>> > https://github.com/rockchip-linux/meta-rockchip/commit/6a139d5b7510c7ba36aace82c239b894d5741cac
>>>> >
>>>> > It was mostly written by Jacob Chen <jacob-chen@iotwrt.com> and I've
>>>> > made a
>>>> > couple small modifications.
>>>> >
>>>> > Signed-off-by: Trevor Woerner <twoerner@gmail.com>
>>>> > ---
>>>> >  recipes-bsp/u-boot/u-boot-rockchip_git.bb | 19 +++++++++++++++++++
>>>> >  1 file changed, 19 insertions(+)
>>>> >  create mode 100644 recipes-bsp/u-boot/u-boot-rockchip_git.bb
>>>> >
>>>> > diff --git a/recipes-bsp/u-boot/u-boot-rockchip_git.bb
>>>> > b/recipes-bsp/u-boot/u-boot-rockchip_git.bb
>>>> > new file mode 100644
>>>> > index 0000000..3b4f109
>>>> > --- /dev/null
>>>> > +++ b/recipes-bsp/u-boot/u-boot-rockchip_git.bb
>>>> > @@ -0,0 +1,19 @@
>>>> > +# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd
>>>> > +# Copyright (C) 2017 Trevor Woerner <twoerner@gmail.com>
>>>> > +# Released under the MIT license (see COPYING.MIT for the terms)
>>>> > +
>>>> > +require recipes-bsp/u-boot/u-boot.inc
>>>> > +
>>>> > +DESCRIPTION = "Rockchip next-dev U-Boot"
>>>> > +LICENSE = "GPLv2+"
>>>> > +LIC_FILES_CHKSUM =
>>>> > "file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6"
>>>> > +COMPATIBLE_MACHINE = "(firefly-rk3288)"
>>>> > +
>>>> > +SRC_URI = "git://github.com/rockchip-linux/u-boot.git;branch=release;"
>>>> > +SRCREV = "${AUTOREV}"
>>>> > +S = "${WORKDIR}/git"
>>>> > +
>>>> > +do_deploy_prepend () {
>>>> > +       # copy to default search path
>>>> > +       cp ${B}/spl/${SPL_BINARY} ${B}/
>>>> > +}
>>>>
>>>> I can't pass build if use do_deploy_prepend instead of
>>>> do_install_prepend.
>>>
>>> It works for me. Did you delete build/tmp?
>>
>> I failed when i did a clean build(delete build dir). I modify
>> do_deploy_prepend to do_install_prepend. Everything is fine.   I guess i can
>> build before because sstate-cache cache the previous build data.
>>>>
>>>>
>>>> > --
>>>> > 2.12.0.rc1.48.g076c053
>>>> >
>>>> > --
>>>> > _______________________________________________
>>>> > yocto mailing list
>>>> > yocto@yoctoproject.org
>>>> > https://lists.yoctoproject.org/listinfo/yocto
>>>> --
>>>> _______________________________________________
>>>> yocto mailing list
>>>> yocto@yoctoproject.org
>>>> https://lists.yoctoproject.org/listinfo/yocto
>>>
>>>
>>


  reply	other threads:[~2017-02-21 22:18 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-19  2:43 [meta-rockchip][PATCH v2 0/5] various updates Trevor Woerner
2017-02-19  2:43 ` [meta-rockchip][PATCH v2 1/5] machine: rk3288: enable SoC-specific assignments Trevor Woerner
2017-02-19  3:40   ` Eddie Cai
2017-02-21 22:25     ` Trevor Woerner
2017-02-22  2:20       ` Eddie Cai
2017-02-26  6:15         ` Trevor Woerner
2017-02-19  2:43 ` [meta-rockchip][PATCH v2 2/5] u-boot-rockchip: add Trevor Woerner
2017-02-19  3:26   ` Eddie Cai
2017-02-19 14:22   ` Jacob Chen
2017-02-19 14:33     ` Eddie Cai
2017-02-20 11:14       ` Eddie Cai
2017-02-21 16:01         ` Trevor Woerner
2017-02-21 22:18           ` Trevor Woerner [this message]
2017-02-22 14:06             ` Eddie Cai
2017-02-27  9:07               ` Trevor Woerner
2017-03-06  5:06                 ` Trevor Woerner
2017-03-06  7:04                   ` Eddie Cai
2017-03-06 18:44                     ` Trevor Woerner
2017-02-19  2:43 ` [meta-rockchip][PATCH v2 3/5] machine: firefly-rk3288: specify bootloader Trevor Woerner
2017-02-19  5:03   ` Eddie Cai
2017-02-19  8:17     ` Jacob Chen
2017-02-21 22:22       ` Trevor Woerner
2017-02-26  6:24         ` Trevor Woerner
2017-02-19  2:43 ` [meta-rockchip][PATCH v2 4/5] classes: rockchip-gpt-img: add Trevor Woerner
2017-02-19  6:32   ` Eddie Cai
2017-02-19  8:31     ` Jacob Chen
2017-02-19 12:18       ` Eddie Cai
2017-02-21 22:21         ` Trevor Woerner
2017-02-27  7:29           ` Trevor Woerner
2017-02-19  2:43 ` [meta-rockchip][PATCH v2 5/5] machine: rk3288: GPT image support Trevor Woerner
2017-02-19  6:33   ` Eddie Cai
2017-02-26  6:28     ` Trevor Woerner

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='CAHUNapSvaH+a2=J09Nx6ff5Kt1LWxf4qtQs6B10YLG+CvOdV6w@mail.gmail.com' \
    --to=twoerner@gmail.com \
    --cc=eddie.cai.linux@gmail.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.