Il 16/07/2014 18:28, Stefan Weil ha scritto:
Debian testing includes a brand new libiscsi, but it does not include libiscsi.pc, so pkg-config won't know that it is available and configure will disable libiscsi.
That's a packaging bug.
I have a patch which fixes this, so QEMU for Debian testing could include libiscsi again. Is a feature regression like this one acceptable? Do we need additional testing (maybe run the build bots with --enable-xxx, so builds fail when xxx no longer works)?
As mentioned in the e49ab19fcaa617ad6cdfe1ac401327326b6a2552 commit message, this was intentional. I was reluctant to do it, but ultimately Peter Lieven convinced me that it isn't just about using fancy new APIs; libiscsi was too buggy to be useful until release 1.8.0 (even 1.9.0 requires a patch to avoid segfaults, and many more if you want to run it on ARM).
Paolo
