> -----Original Message----- > From: Dave Jiang [mailto:dave.jiang@xxxxxxxxx] > Sent: Tuesday, January 03, 2017 9:43 AM ... > > Should that open libpmem.so.1 rather than libpmem.so? (same > > question for the pmemblk engine) > > Hmmm....should we look for either? I have not encountered this issue > on my F25 install. Based on http://www.ibm.com/developerworks/linux/library/l-shlibs/index.html I think fio should only try to open the .so.1 filenames. This ensures compatibility - it won't ever be matched with an incompatible version 2. The non-versioned .so filename is apparently intended only for use by the compiler/linker to find the latest version during compilation. fio links to specific versions of all the libraries selected at compile time - none of these use non-versioned filenames: $ ldd fio linux-vdso.so.1 (0x00007ffc43b5e000) libnuma.so.1 => /lib64/libnuma.so.1 (0x00007f54957db000) librt.so.1 => /lib64/librt.so.1 (0x00007f54955d3000) libaio.so.1 => /lib64/libaio.so.1 (0x00007f54953d1000) libz.so.1 => /lib64/libz.so.1 (0x00007f54951bb000) libm.so.6 => /lib64/libm.so.6 (0x00007f5494eb2000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f5494c92000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f5494a8e000) libc.so.6 => /lib64/libc.so.6 (0x00007f54946c8000) /lib64/ld-linux-x86-64.so.2 (0x0000562b77cec000) Perhaps pmemblk and dev-dax should be restructured to load the libpmem and libpmemblk libraries at startup time like the others. I think that requires adding -lpmem and -lpmemblk to LIBS in the configure script, so they end up in config-host.mak like the others: LIBS+=-ll -lnuma -lrt -laio -lz --- Robert Elliott, HPE Persistent Memory ��.n��������+%������w��{.n�������^n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�
