From: Ian Campbell <Ian.Campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Christoph Egger <Christoph.Egger@amd.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.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 17:12:59 +0000 [thread overview]
Message-ID: <1300900379.10719.42.camel@cthulhu.hellion.org.uk> (raw)
In-Reply-To: <19850.9891.556255.81967@mariner.uk.xensource.com>
On Wed, 2011-03-23 at 16:58 +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"):
> > tools/libxl: move uuid wrapper functions out of line.
> >
> > This isolates users of libxenlight from the need to know about the
> > different OS schemes for UUIDs, in particular the linkage
> > requirements.
> >
> > Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
>
> Thanks for the test, Konrad. I've applied the patch.
I think you forgot to hg add tools/libxl/libxl_uuid.c...
prev parent reply other threads:[~2011-03-23 17:12 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
2011-03-23 16:58 ` Ian Jackson
2011-03-23 17:12 ` Ian Campbell [this message]
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=1300900379.10719.42.camel@cthulhu.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=Christoph.Egger@amd.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.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).