From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com
Subject: 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: Mon, 21 Mar 2011 08:27:27 -0400 [thread overview]
Message-ID: <20110321122727.GA16500@dumpdata.com> (raw)
This is a Fedora Core 13 environment and I just noticed this as I update the xen-unstable
tree:
make -C libxl install
make[3]: Entering directory `/home/konrad/ssd/xtt/xen-unstable/tools/libxl'
rm -f _libxl_paths.h.tmp.tmp; echo "SBINDIR=\"/usr/sbin\"" >> _libxl_paths.h.tmp.tmp; echo "BINDIR=\"/usr/bin\"" >> _libxl_paths.h.tmp.tmp; echo "LIBEXEC=\"/usr/lib/xen/bin\"" >> _libxl_paths.h.tmp.tmp; echo "LIBDIR=\"/usr/lib64\"" >> _libxl_paths.h.tmp.tmp; echo "SHAREDIR=\"/usr/share\"" >> _libxl_paths.h.tmp.tmp; echo "PRIVATE_BINDIR=\"/usr/lib64/xen/bin\"" >> _libxl_paths.h.tmp.tmp; echo "XENFIRMWAREDIR=\"/usr/lib/xen/boot\"" >> _libxl_paths.h.tmp.tmp; echo "XEN_CONFIG_DIR=\"/etc/xen\"" >> _libxl_paths.h.tmp.tmp; echo "XEN_SCRIPT_DIR=\"/etc/xen/scripts\"" >> _libxl_paths.h.tmp.tmp; echo "XEN_LOCK_DIR=\"/var/lock\"" >> _libxl_paths.h.tmp.tmp; if ! cmp _libxl_paths.h.tmp.tmp _libxl_paths.h.tmp; then mv -f _libxl_paths.h.tmp.tmp _libxl_paths.h.tmp; fi
sed -e "s/\([^=]*\)=\(.*\)/#define \1 \2/g" _libxl_paths.h.tmp >_libxl_paths.h.2.tmp
if ! cmp _libxl_paths.h.2.tmp _libxl_paths.h; then mv -f _libxl_paths.h.2.tmp _libxl_paths.h; fi
gcc -Wl,--no-as-needed -o xl xl.o xl_cmdimpl.o xl_cmdtable.o libxlutil.so libxenlight.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
/usr/bin/ld: xl.o: undefined reference to symbol 'xtl_createlogger_stdiostream'
/usr/bin/ld: note: 'xtl_createlogger_stdiostream' is defined in DSO /home/konrad/ssd/xtt/xen-unstable/tools/libxl/../../tools/libxc/libxenctrl.so.4.0 so try adding it to the linker command line
/home/konrad/ssd/xtt/xen-unstable/tools/libxl/../../tools/libxc/libxenctrl.so.4.0: could not read symbols: Invalid operation
collect2: ld returned 1 exit status
make[3]: *** [xl] Error 1
make[3]: Leaving directory `/home/konrad/ssd/xtt/xen-unstable/tools/libxl'
make[2]: *** [subdir-install-libxl] Error 2
make[2]: Leaving directory `/home/konrad/ssd/xtt/xen-unstable/tools'
make[1]: *** [subdirs-install] Error 2
make[1]: Leaving directory `/home/konrad/ssd/xtt/xen-unstable/tools'
make: *** [install-tools] Error 2
And nm --defined | grep stdio shows:
0000000000018da0 t stdiostream_destroy
0000000000018df6 t stdiostream_progress
0000000000018f0a t stdiostream_vmessage
0000000000018cbd T xtl_createlogger_stdiostream
0000000000018dc0 T xtl_stdiostream_adjust_flags
0000000000018cb4 T xtl_stdiostream_set_minlevel
So the symbol is definitly there. Any ideas?
next reply other threads:[~2011-03-21 12:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 12:27 Konrad Rzeszutek Wilk [this message]
2011-03-21 13:05 ` 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 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
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=20110321122727.GA16500@dumpdata.com \
--to=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).