From: akuster808 <akuster808@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: python-cryptography failing to build since openssl upgrade
Date: Wed, 23 Mar 2016 15:01:14 -0700 [thread overview]
Message-ID: <56F3122A.5080303@gmail.com> (raw)
In-Reply-To: <20160323184544.GE2565@jama>
On 03/23/2016 11:45 AM, Martin Jansa wrote:
> 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/
I sent a patch that fixes the current version 1.1 in meta-python.
- armin
>
>>
>> - armin
>>>
>>>
>>>
>> --
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>
>
>
prev parent reply other threads:[~2016-03-23 22:01 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
2016-03-23 22:01 ` akuster808 [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=56F3122A.5080303@gmail.com \
--to=akuster808@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox