All of lore.kernel.org
 help / color / mirror / Atom feed
From: Javier Viguera <javier.viguera@digi.com>
To: <openembedded-devel@lists.openembedded.org>,
	Pushpal Sidhu <psidhu@gateworks.com>, <martin.jansa@gmail.com>
Subject: Re: [meta-python][jethro][PATCH][V2] python-m2crypto: fix SSLv2 symbol issue
Date: Tue, 29 Mar 2016 11:58:55 +0200	[thread overview]
Message-ID: <56FA51DF.3070606@digi.com> (raw)
In-Reply-To: <20160317215442.GL2553@jama>

On 17/03/16 22:54, Martin Jansa wrote:
>
> I'm still seeing multiple issues caused by last openssl upgrade, e.g.
> ruby, pywbem, crda
>
> Are they all supposed to be fixed by this?

Well I just did a basic build tests with the three mentioned above 
(ruby, pywbem and crda) and these are the results:

RUBY
~~~~
I don't see any difference with or without the patch, it's building fine 
even without the patch but the patch does not hurt either.

PYWBEM_0.8.0
~~~~~~~~~~~~
Without the patch fails with:

   File 
"/ssd/dey/jethro/x11/ccimx6sbc/tmp/sysroots/x86_64-linux/usr/lib/python2.7/site-packages/M2Crypto/_m2crypto.py", 
line 24, in swig_import_helper
     _mod = imp.load_module('__m2crypto', fp, pathname, description)
   ImportError: 
/ssd/dey/jethro/x11/ccimx6sbc/tmp/sysroots/x86_64-linux/usr/lib/python2.7/site-packages/M2Crypto/__m2crypto.so: 
undefined symbol: SSLv2_method

With the patch PYWBEM builds fine.

CRDA_3.18
~~~~~~~~~
Without the patch fails with:

NOTE: make -j 8 MAKEFLAGS= 
DESTDIR=/ssd/dey/jethro/x11/ccimx6sbc/tmp/work/cortexa9hf-vfp-neon-dey-linux-gnueabi/crda/3.18-r0/image 
LIBDIR=/usr/lib/crda LDLIBREG=-Wl,-rpath,/usr/lib/crda -lreg all_noverify
   GEN  keys-gcrypt.c
   Trusted pubkeys: pubkeys/linville.key.pub.pem 
pubkeys/sforshee.key.pub.pem
ERROR: Failed to import the "M2Crypto" module: 
/ssd/dey/jethro/x11/ccimx6sbc/tmp/sysroots/x86_64-linux/usr/lib/python2.7/site-packages/M2Crypto/__m2crypto.so: 
undefined symbol: SSLv2_method

With the patch CRDA builds fine.

So I would say that the patch improves the situation. It fixes the build 
for some packages and does not seem to break anything.


I'm also having build failures for CRDA since almost a month now, so I 
would like to have the 'jethro-next' merged to 'jethro' as well.


Thanks,

Javier Viguera


  parent reply	other threads:[~2016-03-29 10:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09 17:06 [meta-python][jethro][PATCH][V2] python-m2crypto: fix SSLv2 symbol issue Armin Kuster
2016-03-09 19:11 ` Martin Jansa
2016-03-09 19:18   ` akuster808
2016-03-14 22:21     ` Pushpal Sidhu
2016-03-17 21:54       ` Martin Jansa
2016-03-17 22:58         ` Pushpal Sidhu
2016-03-29  9:58         ` Javier Viguera [this message]
2016-03-29 10:37           ` Martin Jansa

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=56FA51DF.3070606@digi.com \
    --to=javier.viguera@digi.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=psidhu@gateworks.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.