From: Anthony Wright <anthony@overnetdata.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: xen 4.4.0 dependency lzo fails to build from source due to fPIC
Date: Mon, 28 Jul 2014 22:02:04 +0100 [thread overview]
Message-ID: <53D6BA4C.7080408@overnetdata.com> (raw)
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_init.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?
Any suggestions appreciated.
Anthony.
next reply other threads:[~2014-07-28 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 21:02 Anthony Wright [this message]
2014-07-29 6:46 ` xen 4.4.0 dependency lzo fails to build from source due to fPIC Jan Beulich
2014-07-29 20:21 ` Don Slutz
2014-07-30 7:01 ` Jan Beulich
2014-07-31 1:36 ` Don Slutz
2014-08-01 11:32 ` Anthony Wright
2014-07-30 9:03 ` Anthony Wright
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=53D6BA4C.7080408@overnetdata.com \
--to=anthony@overnetdata.com \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).