From: Martin Jansa <martin.jansa@gmail.com>
To: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH 2/2] opencv: Update to version 3.2
Date: Wed, 25 Jan 2017 15:55:45 +0100 [thread overview]
Message-ID: <20170125145545.GC3260@jama> (raw)
In-Reply-To: <CAPybu_32sRCZGtLQgTzX7bUtqrzfUWawhQy+LJXOCTtO7Q0o3w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]
On Thu, Jan 19, 2017 at 03:21:15PM +0100, Ricardo Ribalda Delgado wrote:
> Hi Martin
>
>
>
> On Thu, Jan 19, 2017 at 12:45 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
> > On Thu, Dec 29, 2016 at 02:35:08PM +0100, Ricardo Ribalda Delgado wrote:
> >> -Only enable protobuf as dependency if dnn module is enabled
> >> -Download manually xfeatures from 3rd party repo
> >> -Remove uneeded fixgcc60patch
> >
> > Fails to build now:
> > http://errors.yoctoproject.org/Errors/Details/117456/
> >
>
>
> I have not been able to replicate it in for qemux86. By looking at the
> error message it looks like something on the freetype module. Until we
> figure out what is going on, maybe we could pakcageconfig that module
> and disable it by default (it is part of contrib)
>
> What do you think?
Yes, it could also be caused by freetype upgrade in oe-core, fine with
me to disable it with packageconfig until the issue is resolved.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
next prev parent reply other threads:[~2017-01-25 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 13:35 [PATCH 1/2] protobuf: Update to latest version 3.1.0 Ricardo Ribalda Delgado
2016-12-29 13:35 ` [PATCH 2/2] opencv: Update to version 3.2 Ricardo Ribalda Delgado
2017-01-19 11:45 ` Martin Jansa
2017-01-19 14:21 ` Ricardo Ribalda Delgado
2017-01-25 14:55 ` Martin Jansa [this message]
2016-12-29 16:00 ` [PATCH 1/2] protobuf: Update to latest version 3.1.0 Khem Raj
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=20170125145545.GC3260@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=ricardo.ribalda@gmail.com \
/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.