Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Joshua Lock <joshua.g.lock@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [fido][PATCH 0/1] Undo ABI breakage in OpenSSL
Date: Thu, 12 May 2016 13:06:33 +0100	[thread overview]
Message-ID: <cover.1463054447.git.joshua.g.lock@intel.com> (raw)

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.

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



             reply	other threads:[~2016-05-12 12:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-12 12:06 Joshua Lock [this message]
     [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 ` [fido][PATCH 0/1] Undo ABI breakage in OpenSSL Martin Jansa
2016-05-13 16:34   ` 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=cover.1463054447.git.joshua.g.lock@intel.com \
    --to=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