From: Olaf Hering <olaf@aepfle.de>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Christoph Egger <Christoph.Egger@amd.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: libxl: link error
Date: Fri, 13 Aug 2010 16:25:52 +0200 [thread overview]
Message-ID: <20100813142552.GA8543@aepfle.de> (raw)
In-Reply-To: <19557.21402.835289.898925@mariner.uk.xensource.com>
On Fri, Aug 13, Ian Jackson wrote:
> If we do that then the .o files in the .a's will be -fPIC too but
> that's a price worth paying.
Even .a objects can endup in other .so files, although its unlikely for
the xen case. Better compile shared libs with -fPIC.
> I guess this might be fallout from Olaf's LDFLAGS/LIBS patch.
Sorry if thats the case, perhaps I should have paid also attention to
the -fPIC usage.
Olaf
next prev parent reply other threads:[~2010-08-13 14:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 8:57 libxl: link error Christoph Egger
2010-08-13 12:29 ` Ian Jackson
2010-08-13 13:37 ` Christoph Egger
2010-08-13 14:11 ` Christoph Egger
2010-08-13 14:15 ` Ian Jackson
2010-08-13 14:25 ` Olaf Hering [this message]
2010-08-13 14:52 ` Ian Jackson
2010-08-16 12:36 ` Gianni Tedesco
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=20100813142552.GA8543@aepfle.de \
--to=olaf@aepfle.de \
--cc=Christoph.Egger@amd.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.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 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).