Comment 11 for bug 1887535

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Two entry points:
a)
$ pull-lp-source qemu focal; cd qemu-4.2
b)
$ git ubuntu clone qemu; cd qemu; git checkout pkg/ubuntu/focal-proposed; dquilt push -a --fuzz=0

And the very same but for groovy.
Running a local build like ./debian/rules build and checking the behavior of submodules.

pull:
Source path /tmp/qemu-4.2
GIT binary git
GIT submodules
C compiler cc
...
sh /tmp/qemu-4.2/scripts/create_config < config-host.mak > config-host.h-timestamp
(GIT="git" "/tmp/qemu-4.2/scripts/git-submodule.sh" ignore )

git:
...
_FORTIFY_SOURCE=2" --extra-ldflags="-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed" --prefix=/usr --sysconfdir=/etc --libdir=/usr/lib/x86_64-linux-gnu --libexecdir=/usr/lib/qemu --firmwarepath=/usr/share/qemu:/usr/share/seabios:/usr/lib/ipxe/qemu --localstatedir=/var --disable-blobs --disable-strip --interp-prefix=/etc/qemu-binfmt/%M --localstatedir=/var --with-git-submodules=ignore \
...
GIT binary git
GIT submodules ui/keycodemapdb tests/fp/berkeley-testfloat-3 tests/fp/berkeley-softfloat-3

Cross verify, without the patch it fails with the new d/rules:
ERROR: unknown option --with-git-submodules=ignore
Try '../../configure --help' for more information

Things are in place as planned and the PKG build in launchpad and such still works fine.
Maybe my testcase is moot :-/
@DDstreet I still see the submodules listed in the configure output, since it is your upstream change and your initial testcase could you have a look at this for SRU verification?