Thomas Huth <th...@redhat.com> writes: > This is the second time in 2 months that compilation with > --disable-replication broke. So instead of relying on reviews here, I > think we should catch this with Patchew / some docker based compilation > test instead that configures the build process with everything disabled, > e.g.: > > ./configure --enable-werror --disable-rdma --disable-slirp \ > --disable-curl --disable-capstone --disable-live-block-migration \ > --disable-glusterfs --disable-replication --disable-coroutine-pool \ > --disable-smartcard --disable-guest-agent --disable-curses \ > --disable-libxml2 --disable-tpm --disable-qom-cast-debug \ > --disable-spice --disable-vhost-vsock --disable-vhost-net \ > --disable-vhost-crypto --disable-vhost-user ... > > (I'm still one of those docker agnostics ... so if someone wants to come > up with a patch, I'd be very glad ... otherwise it'll take some time > 'til I figured it out how to add a docker based test for this...)
In my limited experience, a "disable everything" build requires more frequent tinkering than I'd like. A --disable-all would be nice for this, but I can't spare the time right now. Any takers?
