On Mon, 25 Sep 2023, Shawn Anastasio wrote:
> Change automation build script to call the make defconfig target before
> setting CONFIG_DEBUG and extra options. This fixes issues on Power where
> the build fails without using the ppc64_defconfig.
>
> Signed-off-by: Shawn Anastasio <sanasta...@raptorengineering.com>
> Reported-by: Jan Beulich <jbeul...@suse.com>
What is the problem specifically? Is the issue that CONFIG_DEBUG enabled
before make olddefconfig causes certain DEBUG options also to default to
yes, and these additional options don't work well on Power?
If that is the case, wouldn't it be better to remove the -debug jobs
until they work well on Power? Or make them allow_failure: true ?
> ---
> automation/scripts/build | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/automation/scripts/build b/automation/scripts/build
> index b4edcf010e..19dd9e8270 100755
> --- a/automation/scripts/build
> +++ b/automation/scripts/build
> @@ -22,7 +22,12 @@ if [[ "${RANDCONFIG}" == "y" ]]; then
> # RANDCONFIG implies HYPERVISOR_ONLY
> HYPERVISOR_ONLY="y"
> else
> - echo "CONFIG_DEBUG=${debug}" > xen/.config
> + # Start off with arch's defconfig
> + make -C xen defconfig
> +
> + # Drop existing CONFIG_DEBUG and replace with value of ${debug}
> + sed -i 's/^CONFIG_DEBUG=[yn]//g' xen/.config
> + echo "CONFIG_DEBUG=${debug}" >> xen/.config
>
> if [[ -n "${EXTRA_XEN_CONFIG}" ]]; then
> echo "${EXTRA_XEN_CONFIG}" >> xen/.config
> --
> 2.30.2
>
