Here are the /usr/lib files it installs: --- replaced obj /usr/lib64/pkgconfig/libpci.pc --- replaced dir /usr/lib64/pkgconfig --- replaced obj /usr/lib64/libpci.so.3.0.2 --- replaced sym /usr/lib64/libpci.so.3 --- replaced sym /usr/lib64/libpci.so --- replaced dir /usr/lib64 According to bug #138035 libpci.a was meant to be installed instead of libpci.so* since pciutils-2.2.3-r1: "Dont install libpci.so anymore, but install a PIC libpci.a like Debian."
This .so vs. .a change was done back in 2006. I guess we now have a good reason for providing the .so files only... Let's see what our pciutils-maintainers can say about that.
the issues you refer to are outdated. upstream switched to a shared libpci.
So how am I supposed to build static packages that rely on the presence of libpci.a? ie: kvm-87
(In reply to comment #3) > So how am I supposed to build static packages that rely on the presence of > libpci.a? > ie: kvm-87 > Still cannot build static qemu-kvm without libpci.a Anyone?
This is still broken, no .a file since the bug started, can't build qemu-kvm using the static flag neither. jerome@MobileCPU ~ % gcc -o test test.c -lpci -static /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.3/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lpci collect2: ld returned 1 exit status jerome@MobileCPU ~ % gcc -o test test.c -lpci (succeed)
dont build static apps then. no real good reason for doing so. pciutils-3.1.7-r1 has a USE=static-libs hack for now.
