All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daiane Angolini <daiane.list@gmail.com>
To: Peter Bergin <peter.bergin@tritech.se>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: jethro: cubox-i fetch error
Date: Tue, 12 Jan 2016 11:17:41 -0200	[thread overview]
Message-ID: <CA+jg_OUfvJke=jyAP9B7ydG24iVxPv-3p+aPMrNAOjez6usCbw@mail.gmail.com> (raw)
In-Reply-To: <43F0718C449F6A46B393DA2BEC8E01280C9736C3@post>

On Tue, Jan 12, 2016 at 10:19 AM, Peter Bergin <peter.bergin@tritech.se> wrote:
>
> Hi Daiane,
>
> On 01/12/2016 01:08 PM, Daiane Angolini wrote:
>
> I just faced a fetch error on linux-cubox-i_3.14.14.bb. It looks like the git server was updated somehow.
>
>
> | ERROR: Function failed: Fetcher failure: Fetch command failed with exit code 128, output:
> | The --set-upstream flag is deprecated and will be removed. Consider using --track or --set-upstream-to
> | fatal: 'origin/' is not a valid branch name.
> |
> ERROR: Task 41 (/mnt/code/yocto/jethro/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-cubox-i_3.14.14.bb, do_unpack) failed with exit code '1'
>
>
>
> I think the root cause of this failure is that the variable SRCBRANCH is not set properly for cubox-i in jethro.
>
> # $SRCBRANCH [2 operations]
> #   set? /work/yocto/cubox-i/sources/meta-fsl-arm/recipes-kernel/linux/linux-imx.inc:12
> #     ""
> #   set? /work/yocto/cubox-i/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-cubox-i_3.14.14.bb:10
> #     "linux-linaro-lsk-v3.14-mx6"
> # pre-expansion value:
> #   ""
> SRCBRANCH=""
>
> I think a fix for this is to always set SRCBRANCH in linux-cubox recipe. ( SRCBRANCH ?= --> SRCBRANCH = ). Other kernel recipes in meta-fsl-arm-extra have done this change for jethro. I did this and tested and came to the next conclusion that linux-cubox-i was not ready for gcc5 yet. I have not had possibility to spend more time on this unfortunately.
>

Thanks for letting me know that. I thought it was only a fetch matter
(and I agree with the SRCBRANCH stuff)

:(

Daiane

>
> Build Configuration:
> BB_VERSION        = "1.28.0"
> BUILD_SYS         = "x86_64-linux"
> NATIVELSBSTRING   = "Ubuntu-15.10"
> TARGET_SYS        = "arm-poky-linux-gnueabi"
> MACHINE           = "cubox-i"
> DISTRO            = "poky"
> DISTRO_VERSION    = "2.0"
> TUNE_FEATURES     = "arm armv7a vfp thumb neon callconvention-hard cortexa9"
> TARGET_FPU        = "vfp-neon"
> meta
> meta-yocto        = "HEAD:8a3deca4a4dae430e5434c2f082a4b46bfd5188a"
> meta-oe
> meta-multimedia   = "HEAD:ad6133a2e95f4b83b6b3ea413598e2cd5fb3fd90"
> meta-fsl-arm      = "HEAD:35b8b9bd9863de208ab60e33b55f10ee43e2619b"
> meta-fsl-arm-extra = "HEAD:95f6f731517817ae2f8b379da43ab3376005e5d4"
> meta-fsl-demos    = "HEAD:2231e946e7a94d096394f2b2477e8184c9bbde7b"
>
> Any information is welcomed.
>
> Regards,
> Daiane
>
>
>
>
> The status right now is that cubox-i is broken i jethro.
>
> Regards,
> /Peter
>


  reply	other threads:[~2016-01-12 13:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-12 12:06 jethro: cubox-i fetch error Daiane Angolini
2016-01-12 12:19 ` Peter Bergin
2016-01-12 13:17   ` Daiane Angolini [this message]
2016-01-12 14:27   ` Fabio Estevam
2016-01-12 15:52     ` Daiane Angolini

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='CA+jg_OUfvJke=jyAP9B7ydG24iVxPv-3p+aPMrNAOjez6usCbw@mail.gmail.com' \
    --to=daiane.list@gmail.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=peter.bergin@tritech.se \
    /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.