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

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

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!

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel