On Thu, 8 Jul 2021 at 16:49, Paolo Bonzini <pbonz...@redhat.com> wrote: > > From: Philippe Mathieu-Daudé <f4...@amsat.org> > > Add a target-specific Kconfig. We need the definitions in Kconfig so > the minikconf tool can verify they exits. However CONFIG_FOO is only > enabled for target foo via the meson.build rules. > > Two architecture have a particularity, ARM and MIPS. As their > translators have been split you can potentially build a plain 32 bit > build along with a 64-bit version including the 32-bit subset. > > Signed-off-by: Philippe Mathieu-Daudé <f4...@amsat.org> > Message-Id: <20210131111316.232778-6-f4...@amsat.org> > Signed-off-by: Alex Bennée <alex.ben...@linaro.org> > Reviewed-by: Thomas Huth <th...@redhat.com> > Message-Id: <20210707131744.26027-2-alex.ben...@linaro.org> > Signed-off-by: Paolo Bonzini <pbonz...@redhat.com>
Hi; this change (commit f4063f9c319e392 in master) seems to have resulted in qemu-system-tricore no longer building the 'tricore_testboard'. Before this commit: $ ./build/tricore/qemu-system-tricore -M help Supported machines are: KIT_AURIX_TC277_TRB Infineon AURIX TriBoard TC277 (D-Step) none empty machine tricore_testboard a minimal TriCore board After this commit, 'tricore_testboard' no longer appears in the list. The hw/tricore/meson.build uses "when: 'CONFIG_TRICORE'" to compile the source files for the board, so presumably that CONFIG switch is no longer being defined ? This in turn breaks 'make check-tcg' for builds which build tricore-softmmu, because some of the tests there want to run code on the tricore_testboard: [...] RUN tests for tricore TEST test_abs.tst on tricore qemu-system-tricore: unsupported machine type Use -machine help to list supported machines ../Makefile.target:168: recipe for target 'run-test_abs.tst' failed (I guess we're not running "check-tcg" in gitlab CI. I do run it locally, but only on a linux-user-only build tree, which is why I didn't see this earlier.) thanks -- PMM
