On 5/6/21 2:00 AM, Thomas Huth wrote: > D'oh! I think I can work-around the problem with a patch like > this on top: > > diff a/configure b/configure > --- a/configure > +++ b/configure > @@ -1686,6 +1686,11 @@ fi > > for config in $mak_wilds; do > target="$(basename "$config" .mak)" > + if [ "$target" = "moxie-softmmu" ]; then > + # This is a work-around to make incremental builds pass after > + # moxie-softmmu has been removed. It can be removed later. > + continue > + fi > if echo "$target_list_exclude" | grep -vq "$target"; then > default_target_list="${default_target_list} $target" > fi > diff a/default-configs/targets/moxie-softmmu.mak > b/default-configs/targets/moxie-softmmu.mak > new file mode 100644 > index 0000000000..23fd596b66 > --- /dev/null > +++ b/default-configs/targets/moxie-softmmu.mak > @@ -0,0 +1,2 @@ > +# This is just a dummy file to avoid that incremental builds are failing.
s/to avoid that incremental builds are failing/to avoid incremental build failures/ > +# It can be removed as soon as all builders have been updated. > > Does that look acceptable? If yes, I'll respin my PR with that > squashed into the moxie patch. > > Thomas > > -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3226 Virtualization: qemu.org | libvirt.org