Re: Automated report: NetBSD-current/i386 build failure

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

I don't know if it is to do with similar, but I am getting on amd64:
...
#      link  XEN3_DOM0/netbsd
/home/sysbuild/amd64/tools/bin/x86_64--netbsd-ld -Map netbsd.map
--cref -T netbsd.ldscript -Ttext 0xffffffff80200000 -e start -X -o
netbsd ${SYSTEM_OBJ:[@]:Nswapnetbsd.o} ${EXTRA_OBJ} vers.o
swapnetbsd.o
/home/sysbuild/amd64/tools/bin/x86_64--netbsd-ld: acpi_machdep.o: in
function `acpi_md_intr_mask':
acpi_machdep.c:(.text+0x7ad): undefined reference to `intr_mask'
/home/sysbuild/amd64/tools/bin/x86_64--netbsd-ld: acpi_machdep.o: in
function `acpi_md_intr_unmask':
acpi_machdep.c:(.text+0x7b2): undefined reference to `intr_unmask'
*** [netbsd] Error code 1
nbmake[2]: stopped in
/home/sysbuild/amd64/obj/home/sysbuild/src/sys/arch/amd64/compile/XEN3_DOM0
...

On Sun, 22 Dec 2019 at 23:29, Robert Elz <kre%munnari.oz.au@localhost> wrote:
>
>     Date:        Sun, 22 Dec 2019 19:37:08 +0000 (UTC)
>     From:        NetBSD Test Fixture <bracket%NetBSD.org@localhost>
>     Message-ID:  <157704342880.16885.13334931433571245450%babylon5.NetBSD.org@localhost>
>
>   | This is an automatically generated notice of a NetBSD-current/i386
>   | build failure.
>
> Was caused by
>
>   | The following commits were made between the last successful build and
>   | the failed build:
>   |
>   |     2019.12.22.15.57.06 thorpej src/sys/arch/arm/acpi/acpi_machdep.c,v 1.11
>   |     2019.12.22.15.57.06 thorpej src/sys/arch/arm/include/acpi_machdep.h,v 1.3
>   |     2019.12.22.15.57.06 thorpej src/sys/arch/ia64/acpi/acpi_machdep.c,v 1.10
>   |     2019.12.22.15.57.07 thorpej src/sys/arch/ia64/include/acpi_machdep.h,v 1.9
>   |     2019.12.22.15.57.07 thorpej src/sys/arch/x86/acpi/acpi_machdep.c,v 1.29
>   |     2019.12.22.15.57.07 thorpej src/sys/arch/x86/include/acpi_machdep.h,v 1.14
>   |     2019.12.22.15.57.07 thorpej src/sys/dev/acpi/acpi_intr.h,v 1.4
>   |     2019.12.22.15.57.07 thorpej src/sys/dev/acpi/acpi_util.c,v 1.16
>
> and results from (the new?) intr_mask() and intr_unmask() not being
> provided for the XEN3PAE_DOM0 kernel.
>
> There are 3 distinctions in that: it is !MULTIPROCESOR, it is PAE,
> and it is XEN ... which of those (or perhaps even a combination)
> is the reason that the function definitions are not included I don't
> know - the intricacies of low level x86 hardware management are not
> something I ever want to learn about...
>
> Note: this is where the build stopped, whether other kernels would have
> also been affected had the build not stopped there is (to me) unknown.
>
> Jason, can you please take a look.
>
> kre
>


-- 
----