From mboxrd@z Thu Jan  1 00:00:00 1970
From: Anthony Wright <anthony@overnetdata.com>
Subject: Re: xen 4.4.0 dependency lzo fails to build from source
 due to fPIC
Date: Wed, 30 Jul 2014 10:03:24 +0100 (BST)
Message-ID: <11442088.0.1406711004427.JavaMail.root@zimbra.overnetdata.com>
References: <53D75F700200007800027174@mail.emea.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <53D75F700200007800027174@mail.emea.novell.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xen.org
List-Id: xen-devel@lists.xenproject.org

----- Original Message -----
> >>> On 28.07.14 at 23:02, <anthony@overnetdata.com> wrote:
> > If xen detects lzo, it tries to build
> > tools/xclib/libxenguest.so.4.4.0
> > with lzo support but fails with the error:
> >
> > /usr/bin/ld:
> > /usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.2/../../../../lib64/liblzo2.a(lzo_ini
> > t.o):
> > relocation R_X86_64_PC32 against symbol '_lzo_config_check' can not
> > be
> > used when making a shared object; recompile with -fPIC
> >
> > reading around the subject it would seem to be a problem with the
> > lzo
> > library (2.08) which has been built without using the -fPIC option.
> > However, when I look at the lzo package there is no standard way to
> > build it with -fPIC. My workaround has been simply to remove the lzo
> > package, but I'm not sure this is a good solution, and I don't
> > understand why this problem doesn't seem to have been encountered
> > before.
> >
> > Should I be building Xen with LZO support? (does everybody else
> > build
> > without LZO support?)
> >
> > Should I be adding fPIC to the LZO options and rebuilding LZO?
> >
> > Is there something else I'm doing wrong that is causing the problem?
> 
> The expectation is that there is a shared library to link against, not
> just a static one. If you want the static-only case supported, then
> you'll need to contribute patches (and imo those should then cover
> not just lzo, but all of the compression methods other than lz4).
> 
> Jan

Thanks, I rebuilt the lzo2 library with the --enable-shared option, and it successfully built.