All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yannick Calmettes <yannick.calmettes@analogway.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
	 Gustavo Ramon Arambula Aguilar <gustavo.arambula@freescale.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: Can't build meta-toolchain-qt5 on 3.14.28-1.0.0ga
Date: Wed, 22 Apr 2015 14:04:51 +0200	[thread overview]
Message-ID: <55378E63.9040509@analogway.com> (raw)
In-Reply-To: <CAP9ODKrKM33t7H7a0+6=nRibsccxUA0XZ0+X3XtNV6Cd=uxFVQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2099 bytes --]

Dear Otavio,

It works on Dizzy branch too but the problem is that I have debug problems.
When I debug my application that was compiled with Dizzy QT tool-chain 
on a target that have 3.14.28-1.0.0ga QT libraries, I have library 
incompatibility error in QT Creator.

Best,

Yannick
**
Le 22/04/2015 13:14, Otavio Salvador a écrit :
> On Tue, Apr 21, 2015 at 4:42 PM, Gustavo Ramon Arambula Aguilar
> <gustavo.arambula@freescale.com> wrote:
>> We have a customer that reported a problem when baking the
>> meta-toolchain-qt5 on 3.14.28-1.0.0ga. I reproduced the error and indeed
>> there are some bluez dependencies issues and some fetching issues.
>>
>>
>>
>> Have you seen this before? How may this be fixed? Is the fetching error a
>> problem from our side?
>>
>>
>>
>> ERROR: Multiple .bb files are due to be built which each provide
>> virtual/bluez
>> (/home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/sources/poky/meta/recipes-connectivity/bluez/bluez4_4.101.bb
>> /home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/sources/meta-fsl-bsp-release/imx/meta-fsl-bluez/recipes-connectivity/bluez5/bluez5_5.25.bb).
>>
>>
>>
>> This usually means one provides something the other doesn't and should.
>>
>>
>>
>> ERROR: Fetcher failure: Unable to find revision
>> aa651c73bf7bc57c1b6b1bfcfa9afe901884a102 in branch 5.3 even from upstream
>>
>> ERROR: Function failed: Fetcher failure for URL:
>> 'git://qt.gitorious.org/qt/qtsystems.git;branch=5.3'. Unable to fetch URL
>> from any source.
>>
>> ERROR: Logfile of failure stored in:
>> /home/usuario/fsl-release-bsp/buildimx6q/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/qtsystems/5.3.99+5.4.0-beta1+gitAUTOINC+aa651c73bf-r0/temp/log.do_fetch.23039
>>
>> ERROR: Task 909
>> (/home/usuario/fsl-release-bsp/sources/meta-qt5/recipes-qt/qt5/qtsystems_git.bb,
>> do_fetch) failed with exit code '1'
>>
>>
>>
>> The original thread is:
>>
>> https://community.freescale.com/thread/352283
> Please try with FSL Community BSP Fido branch. I think it'll work out of box.
>


 

[-- Attachment #2: Type: text/html, Size: 3565 bytes --]

  reply	other threads:[~2015-04-22 12:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21 19:42 Can't build meta-toolchain-qt5 on 3.14.28-1.0.0ga Gustavo Ramon Arambula Aguilar
2015-04-22 11:14 ` Otavio Salvador
2015-04-22 12:04   ` Yannick Calmettes [this message]
2015-04-22 12:13     ` Otavio Salvador
2015-04-22 12:21       ` Yannick Calmettes
2015-04-22 12:28         ` Otavio Salvador
2015-04-24 17:09     ` Gustavo Ramon Arambula Aguilar
2015-04-27  7:26       ` Yannick Calmettes
2015-04-27 13:35         ` Lauren Post
2015-04-27 16:54           ` Gustavo Ramon Arambula Aguilar

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=55378E63.9040509@analogway.com \
    --to=yannick.calmettes@analogway.com \
    --cc=gustavo.arambula@freescale.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.