Closed GoogleCodeExporter closed 9 years ago
What steps will reproduce the problem? 1. git clone git://git.qemu.org/qemu.git 2. cd qemu 3, git reset --hard v1.3.0 4. cp ../hlfs/patches/hlfs_driver_for_qemu.patch ./ 5. patch -p1 < hlfs_driver_for_qemu.patch 6, Modify the dead path 7, ./configure 8, make 9, ldd ./qemu-img What is the expected output? What do you see instead? Expected output: 1, No warnings, errors. 2, lib*.so points to what i think. See instead: 1, Some warnings, see attach file for details. 2, lib*.so points to what i cannot understand! jiawei@jiawei-laptop:~/workshop4/qemu$ ldd ./qemu-img linux-gate.so.1 => (0x003f0000) librt.so.1 => /lib/tls/i686/cmov/librt.so.1 (0x00636000) libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0x00781000) libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x00179000) libz.so.1 => /lib/libz.so.1 (0x0053f000) libhlfs.so => /usr/lib/libhlfs.so (0x00285000) liblog4c.so.3 => not found libhdfs.so.0 => not found libjvm.so => /usr/lib/libjvm.so (0x00e00000) libpthread.so.0 => /lib/tls/i686/cmov/libpthread.so.0 (0x008c5000) libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0x11bbf000) /lib/ld-linux.so.2 (0x0015c000) libhdfs.so.0 => /home/jiawei/workshop1/cloudxy/trunk/hlfs/build/../3part/hadoop/lib32/libhdfs.so.0 (0x00607000) liblog4c.so.3 => /home/jiawei/workshop1/cloudxy/trunk/hlfs/build/../3part/log/lib32/liblog4c.so.3 (0x00398000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x003f1000) libm.so.6 => /lib/tls/i686/cmov/libm.so.6 (0x00110000) libdl.so.2 => /lib/tls/i686/cmov/libdl.so.2 (0x00136000) libexpat.so.1 => /lib/libexpat.so.1 (0x0032b000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00674000) My key lib/include paths in qemu/configure file changed like following: [...] 2838 GLIB_DIR1_INC=/usr/lib/glib-2.0/include 2839 GLIB_DIR2_INC=/usr/include/glib-2.0 2840 HLFS_DIR=/home/jiawei/workshop3/hlfs 2841 LOG4C_DIR=$HLFS_DIR/3part/log 2842 HDFS_DIR=$HLFS_DIR/3part/hadoop 2843 JVM_DIR=/usr/lib/jvm/java-6-openjdk 2844 2845 if [ `getconf LONG_BIT` -eq "64" ];then 2846 CLIBS="-L$LOG4C_DIR/lib64" 2847 CLIBS="-L$HDFS_DIR/lib64 $CLIBS" 2848 CLIBS="-L$HLFS_DIR/output/lib64 $CLIBS" 2849 CLIBS="-L$JVM_DIR/jre/lib/amd64/server/ $CLIBS" 2850 fi 2851 2852 if [ `getconf LONG_BIT` -eq "32" ];then 2853 CLIBS="-L$LOG4C_DIR/lib32" 2854 CLIBS="-L$HDFS_DIR/lib32 $CLIBS" 2855 CLIBS="-L$JVM_DIR/jre/lib/i386/server $CLIBS" 2856 CLIBS="-L$HLFS_DIR/output/lib32 $CLIBS" 2857 fi 2858 2859 CFLAGS="-I$GLIB_DIR1_INC" 2860 CFLAGS="-I$GLIB_DIR2_INC $CFLAGS" 2861 CFLAGS="-I$HLFS_DIR/src/include $CFLAGS" 2862 CFLAGS="-I$LOG4C_DIR/include $CFLAGS" 2863 2864 hlfs_libs="$CLIBS -lhlfs -llog4c -lglib-2.0 -lgthread-2.0 -lrt -lhdfs -ljvm" 2865 if compile_prog "$CFLAGS" "$CLIBS $hlfs_libs" ; then 2866 hlfs=yes 2867 libs_tools="$hlfs_libs $libs_tools" 2868 libs_softmmu="$hlfs_libs $libs_softmmu" 2869 else 2870 if test "$hlfs" = "yes" ; then 2871 feature_not_found "hlfs block device" 2872 fi 2873 hlfs=no 2874 fi 2875 fi [...] I cannot understand why libhdfs.so.0 => /home/jiawei/workshop1/cloudxy/trunk/hlfs/build/../3part/hadoop/lib32/libhdfs.so .0 (0x00607000) liblog4c.so.3 => /home/jiawei/workshop1/cloudxy/trunk/hlfs/build/../3part/log/lib32/liblog4c.so.3 (0x00398000)?
Original issue reported on code.google.com by harryxi...@gmail.com on 21 Jan 2013 at 6:00
harryxi...@gmail.com
Attachments:
Original comment by kanghua...@gmail.com on 9 Feb 2013 at 6:25
kanghua...@gmail.com
Original issue reported on code.google.com by
harryxi...@gmail.com
on 21 Jan 2013 at 6:00Attachments: