From: Martin Jansa <martin.jansa@gmail.com>
To: Joshua Lock <joshua.g.lock@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [fido][PATCH 0/1] Undo ABI breakage in OpenSSL
Date: Thu, 12 May 2016 16:16:45 +0200 [thread overview]
Message-ID: <20160512141645.GA2567@jama> (raw)
In-Reply-To: <cover.1463054447.git.joshua.g.lock@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1972 bytes --]
On Thu, May 12, 2016 at 01:06:33PM +0100, Joshua Lock wrote:
> The backported upgrade to OpenSSL 1.0.2h introduced a newer version of
> Debian's linker version-script which breaks the OpenSSL ABI.
> This isn't desirable for a stable release, thus the attached patch reverts
> the linker-version changes and simply adds the 2 new symbols required by
> 1.0.2h.
>
> Thanks to Martin Jansa for spotting the issue and suggesting a fix.
Thanks for following it and getting it merged so quickly.
It was already merged in fido, can we get the same to jethro (which was
also recently upgraded to 1.0.2h)?
Small downside is that the same 1.0.2h version in fido and jethro will
have different ABI than 1.0.2h in krogoth (unless someone updates the
version there as suggested by Andre in:
http://lists.openembedded.org/pipermail/openembedded-core/2016-March/118433.html
).
Krogoth was released with this ABI, so it's something users have
to deal with when upgrading to newer Yocto release (and this won't be
the only component with different ABI).
> The following changes since commit e7c46ce3e59cb4fd770e76ae006c0166d0dd5265:
>
> build-appliance-image: Update to fido head revision (2016-05-11 18:00:15 +0100)
>
> are available in the git repository at:
>
> git://git.openembedded.org/openembedded-core-contrib joshuagl/fido-next
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=joshuagl/fido-next
>
> Joshua Lock (1):
> openssl: prevent ABI break from earlier fido releases
>
> .../openssl/debian1.0.2/version-script.patch | 31 +++++++++++++++-------
> 1 file changed, 22 insertions(+), 9 deletions(-)
>
> --
> 2.5.5
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
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-05-12 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 12:06 [fido][PATCH 0/1] Undo ABI breakage in OpenSSL Joshua Lock
[not found] ` <cover.1463054731.git.joshua.g.lock@intel.com>
2016-05-12 12:06 ` [fido][PATCH 1/1] openssl: prevent ABI break from earlier fido releases Joshua Lock
2016-05-12 14:16 ` Martin Jansa [this message]
2016-05-13 16:34 ` [fido][PATCH 0/1] Undo ABI breakage in OpenSSL Richard Purdie
2016-05-13 20:59 ` akuster808
2016-05-13 23:50 ` 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=20160512141645.GA2567@jama \
--to=martin.jansa@gmail.com \
--cc=joshua.g.lock@intel.com \
--cc=openembedded-core@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