All of lore.kernel.org
 help / color / mirror / Atom feed
From: Subodh Chiwate <subodh.chiwate@ufomoviez.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: Build failing with [imx-vpu, imx-lib : LIC_FILES_CHKSUM points to an invalid file] error after repo sync
Date: Mon, 29 Dec 2014 18:00:08 +0530	[thread overview]
Message-ID: <54A14950.4060706@ufomoviez.com> (raw)
In-Reply-To: <CAP9ODKpW8DXL8Hohi+p=qQJKdts9b-u_ZSy2wOR=4prj6uhN0w@mail.gmail.com>

Hi Otavio,
Thanks for guidance.
I will start setting up the community BSP setup ASAP.
Also created a fresh setup for the 3.10.31-beta earlier today and it is
compiling (in progress).
Hopefully I can freeze it by today and move to Dizzy immediately.

On 12/29/2014 04:45 PM, Otavio Salvador wrote:
> Hello Subodh,
>
> On Mon, Dec 29, 2014 at 5:03 AM, Subodh Chiwate
> <subodh.chiwate@ufomoviez.com> wrote:
>> I have been unable to trace root cause of the following problem.
>> Could you please suggest a way for me to restore my setup.
> I strongly advise you to move to the FSL Community BSP. As I don't
> know your project's roadmap it is hard to properly advise regarding
> which is the most adequate branch to use.
>
> I think you should stay away from 3.10.31 for now as it is a beta
> release and not yet ready for production use. I suggest you to use
> Dizzy (which uses 3.10.17-1.0.2 GA).
>
> Anyway, I just built 'imx-vpu' at my end (using today's version) and
> it worked just fine. See the below log (log.do_configure) file for
> confirmation:
>
> DEBUG: Executing python function sysroot_cleansstate
> DEBUG: Python function sysroot_cleansstate finished
> DEBUG: Executing shell function do_configure
> DEBUG: Shell function do_configure finished
> DEBUG: Executing python function do_qa_configure
> NOTE: Checking autotools environment for common misconfiguration
> NOTE: imx-vpu: md5 checksum matched for
> file://vpu/EULA.txt;md5=b063366b066c9f10037c59756a9ced54
> DEBUG: Python function do_qa_configure finished
>
> Regards,
>

--
Regards,
Subodh

-- **************** CAUTION - Disclaimer ***************** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. UFOMoviez India Ltd. has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. UFOMoviez India Ltd. reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the UFOMoviez India Ltd.'s e-mail system. ***************** End of Disclaimer *******************


      reply	other threads:[~2014-12-29 12:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 10:07 Build failing with [imx-vpu, imx-lib : LIC_FILES_CHKSUM points to an invalid file] error after repo sync Subodh Chiwate
2014-12-29  7:03 ` Subodh Chiwate
2014-12-29 11:15   ` Otavio Salvador
2014-12-29 12:30     ` Subodh Chiwate [this message]

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=54A14950.4060706@ufomoviez.com \
    --to=subodh.chiwate@ufomoviez.com \
    --cc=meta-freescale@yoctoproject.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 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.