Hi Jeremy,

I don't know if this can help, but when I compile a kernel I perform =20
these steps :
( my directory containing "src" & "xsrc" is /CROSSCOMP/BUILD/ )

-1- Build the toolchain :
./build.sh -N 1 -j 3 -m i386 -O /CROSSCOMP/BUILD/obj.i386 -T /=20
CROSSCOMP/BUILD/tools.i386 -D /CROSSCOM
P/BUILD/dest.i386 -R /CROSSCOMP/BUILD/release.i386 -X /CROSSCOMP/=20
BUILD/xsrc -U -x tools

-2- Build the Kernel :
./build.sh -N 1 -j 3 -m i386 -O /CROSSCOMP/BUILD/obj.i386 -T /=20
CROSSCOMP/BUILD/tools.i386 -D /CROSSCOM
P/BUILD/dest.i386 -R /CROSSCOMP/BUILD/release.i386 -X /CROSSCOMP/=20
BUILD/xsrc -U -x -u kernel=3DMYKERNEL

I'm not sure you could both use "tools" & "kernel" on the same =20
command line ...

But I haven't tested to compile for ARCH XEN. I only know it works =20
perfectly with i386 / amd64 / sparc64 / macppc ( I tested it )

Best Regards,

Arnaud.

Le 26 juil. 06 =E0 21:21, reed@reedmedia.net a =E9crit :

> I looked at NetBSD/Xen howto but don't see how to build my own custom
> kernel.
>
> (Something changed and even though I used the PF module for two =20
> weeks I
> can't use it any more.)
>
> I copied sys/arch/i386/conf/XEN2_DOMU to sys/arch/i386/conf/=20
> XEN2_DOMU_PF.
>
> (I am using XEN2 since I am currently using XENU.)
>
> Then I ran:
>
> ./build.sh -m xen -a i386 tools kernel=3DXEN2_DOMU_PF
>
> It failed after building tools with:
>
> =3D=3D=3D> Tools built to /usr/src/netbsd-3/src/obj/=20
> tooldir.NetBSD-3.99.21-i386
> =3D=3D=3D> Building kernel:  XEN2_DOMU_PF
> =3D=3D=3D> Build directory:
> /usr/src/netbsd-3/src/sys/arch/xen/compile/obj/XEN2_DOMU_PF
> rm -f a.out [Ee]rrs mklog core *.core .gdbinit
> config: cannot read /usr/src/netbsd-3/src/sys/arch/xen/conf/=20
> XEN2_DOMU_PF:
> No such file or directory
>
> ERROR: nbconfig failed for XEN2_DOMU_PF
> *** BUILD ABORTED ***
>
> I see it is using wrong directory above.
>
> What is correct way to build NetBSD/Xen kernels?
>
> Am I not supposed to use "-m xen"?
>
> How does the release team build them?
>
> Thanks,
>
> Jeremy C. Reed
>
> p.s. Once I figure this out, I can add to the NetBSD/Xen howto.
>