From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: akuster@mvista.com
Subject: Re: python-cryptography failing to build since openssl upgrade
Date: Wed, 23 Mar 2016 19:45:44 +0100 [thread overview]
Message-ID: <20160323184544.GE2565@jama> (raw)
In-Reply-To: <56F2C274.8070105@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]
On Wed, Mar 23, 2016 at 09:21:08AM -0700, akuster808 wrote:
>
>
> On 03/17/2016 02:49 PM, Martin Jansa wrote:
> > On Wed, Mar 09, 2016 at 08:50:49PM +0100, Martin Jansa wrote:
> >> Do we really need to use that version script for openssl?
> >>
> >> Here is another failure:
> >> http://errors.yoctoproject.org/Errors/Details/54984/
> >>
> >> in our local builds we use couple prebuild binaries from 3rdparty, which
> >> now aren't compatible with openssl ABI (possibly because of
> >> version-script update:
> >> http://lists.openembedded.org/pipermail/openembedded-core/2016-March/118433.html
> >> )
> >
> > Still failing:
> > http://errors.yoctoproject.org/Errors/Details/56595/
>
> will look into it today.
Thanks, I've tried to upgrade it to 1.2.3 (patch is on ML), but that also fails, just
with different error:
http://errors.yoctoproject.org/Errors/Details/57058/
>
> - armin
> >
> >
> >
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2016-03-23 18:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 19:50 python-cryptography failing to build since openssl upgrade Martin Jansa
2016-03-17 21:49 ` Martin Jansa
2016-03-23 16:21 ` akuster808
2016-03-23 18:45 ` Martin Jansa [this message]
2016-03-23 22:01 ` akuster808
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=20160323184544.GE2565@jama \
--to=martin.jansa@gmail.com \
--cc=akuster@mvista.com \
--cc=openembedded-devel@lists.openembedded.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.