From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Christoph Egger <Christoph.Egger@amd.com>
Subject: Re: Build problem: note: 'xtl_createlogger_stdiostream' is defined in DSO .. so try adding it to the linker command line... libxenctrl.so.4.0: could not read symbols: Invalid operation
Date: Wed, 23 Mar 2011 11:52:55 -0400 [thread overview]
Message-ID: <20110323155254.GA24172@dumpdata.com> (raw)
In-Reply-To: <1300893178.5195.4.camel@cthulhu.hellion.org.uk>
On Wed, Mar 23, 2011 at 03:12:58PM +0000, Ian Campbell wrote:
> On Tue, 2011-03-22 at 17:25 +0000, Ian Campbell wrote:
> > On Tue, 2011-03-22 at 17:16 +0000, Konrad Rzeszutek Wilk wrote:
> > > On Mon, Mar 21, 2011 at 03:53:25PM +0000, Ian Campbell wrote:
> > > > On Mon, 2011-03-21 at 14:53 +0000, Ian Jackson wrote:
> > > > > Ian Campbell writes ("Re: [Xen-devel] Build problem: note: 'xtl_createlogger_stdiostream' is defined in DSO .. so try adding it to the linker command line... libxenctrl.so.4.0: could not read symbols: Invalid operation"):
> > > > > > xl: link against libxenctrl
> > > > >
> > > > > I've applied this, thanks. Although I don't understand why the build
> > > > > failed for Konrad and not me or my test system.
> > > >
> > > > Me neither.
> > >
> > > I am not sure either. Here is another with todays pull:
> > >
> > > gcc -o xl xl.o xl_cmdimpl.o xl_cmdtable.o libxlutil.so -L/home/konrad/ssd/xtt/xen-unstable/tools/libxl/../../tools/libxl -Wl,-rpath-link=/home/konrad/ssd/xtt/xen-unstable/tools/libxl/../../tools/libxc -Wl,-rpath-link=/home/konrad/ssd/xtt/xen-unstable/tools/libxl/../../tools/xenstore -Wl,-rpath-link=/home/konrad/ssd/xtt/xen-unstable/tools/libxl/../../tools/blktap2/control -lxenlight -L/home/konrad/ssd/xtt/xen-unstable/tools/libxl/../../tools/libxc -lxenctrl
> > > /usr/bin/ld: xl_cmdimpl.o: undefined reference to symbol 'uuid_parse@@UUID_1.0'
> > > /usr/bin/ld: note: 'uuid_parse@@UUID_1.0' is defined in DSO /lib64/libuuid.so.1 so try adding it to the linker command line
> > > /lib64/libuuid.so.1: could not read symbols: Invalid operation
> >
> > This is due to the use of the uuid library being inlined in the libxl
> > headers, so the user of libxl can end up with linking requirements due
> > to libxl header internals. I think the right fix is to move these out of
> > line like I did with essentially the same thing in blktap2. I'll take a
> > look shortly.
>
> Konrad, Jeremy,
>
> Does this help?
Yes!
next prev parent reply other threads:[~2011-03-23 15:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 12:27 Build problem: note: 'xtl_createlogger_stdiostream' is defined in DSO .. so try adding it to the linker command line... libxenctrl.so.4.0: could not read symbols: Invalid operation Konrad Rzeszutek Wilk
2011-03-21 13:05 ` Ian Campbell
2011-03-21 14:53 ` Ian Jackson
2011-03-21 15:53 ` Ian Campbell
2011-03-22 17:16 ` Konrad Rzeszutek Wilk
2011-03-22 17:25 ` Ian Campbell
2011-03-23 15:12 ` Ian Campbell
2011-03-23 15:52 ` Konrad Rzeszutek Wilk [this message]
2011-03-23 16:58 ` Ian Jackson
2011-03-23 17:12 ` Ian Campbell
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=20110323155254.GA24172@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Christoph.Egger@amd.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=jeremy@goop.org \
--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).