Date: Sat, 07 Aug 2004 00:21:24 -0600 From: Scott Long <scottl@samsco.org> To: andrew.lankford@verizon.net Cc: current@freebsd.org Subject: Re: cvs commit: src/sys/amd64/amd64 mp_machdep.c Message-ID: <411474E4.8030100@samsco.org> In-Reply-To: <20040807041621.JWTS24490.out014.verizon.net@outgoing.verizon.net> References: <20040807041621.JWTS24490.out014.verizon.net@outgoing.verizon.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrew Lankford wrote: >>Hmm. I was able to build an amd64 SMP kernel and an amd64 >>UP kernel on sledge.freebsd.org following the last batch >>of commits. Could you confirm your source is in sync: in >>particular, sys/amd64/amd64/mem.c is revision >>1.120, and sys/conf/files.amd64 is revision 1.44? In my >local source snapshot, M_DECLARE(M_MEMDESC) appears in >>memrange.h, and the M_DEFINE(M_MEMDESC, ...) is in mem.c. > > > Yes, yes, and yes, assuming you meant "MALLOC_DEFINE" > instead of "M_DEFINE",etc . I just uncommented "device mem" > and "device io" from my kernel config and the kernel built > and installed ok, along with mem.ko (even though I can't see > what purpose itt would serve when it's already compiled in > statically). > > Once again, I'll attach the kernel config file that caused > buildkernel to stop and complain. > > Andrew Lankford > I just fixed this. Thanks for sending your kernel config. Note that you probably shouldn't remove the acpi driver from the kernel config since it's practically mandatory on amd64 and won't load correctly from the bootloader. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?411474E4.8030100>