Date: Tue, 7 Sep 2004 18:48:11 -0500 From: "Conrad J. Sabatier" <conrads@cox.net> To: freebsd-questions@freebsd.org Subject: Re: complie kernel in amd 64 Message-ID: <20040907184811.12372211@dolphin.local.net> In-Reply-To: <20040907210828.8386.qmail@web21203.mail.yahoo.com> References: <20040907210828.8386.qmail@web21203.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 8 Sep 2004 05:08:28 +0800 (CST), adrian kok <adriankok2000@yahoo.com.hk> wrote: > Hi all > > I try to add ipfw (default -accept), device polling in > the kernel and recomplie in amd 64 > > but I got error as follows: > > how can I fix it > > Thank you > > > > ../../../amd64/amd64/genassym.c:209: error: storage > size of `MSR_FSBASEw2' isn't known > ../../../amd64/amd64/genassym.c:209: error: storage > size of `MSR_FSBASEw3' isn't known > ../../../amd64/amd64/genassym.c:210: error: storage > size of `MSR_GSBASEsign' isn't known > ../../../amd64/amd64/genassym.c:210: error: storage > size of `MSR_GSBASEw0' isn't known > ../../../amd64/amd64/genassym.c:210: error: storage > size of `MSR_GSBASEw1' isn't known > ../../../amd64/amd64/genassym.c:210: error: storage > size of `MSR_GSBASEw2' isn't known > ../../../amd64/amd64/genassym.c:210: error: storage > size of `MSR_GSBASEw3' isn't known > ../../../amd64/amd64/genassym.c:211: error: storage > size of `MSR_KGSBASEsign' isn't known > ../../../amd64/amd64/genassym.c:211: error: storage > size of `MSR_KGSBASEw0' isn't known > ../../../amd64/amd64/genassym.c:211: error: storage > size of `MSR_KGSBASEw1' isn't known > ../../../amd64/amd64/genassym.c:211: error: storage > size of `MSR_KGSBASEw2' isn't known > ../../../amd64/amd64/genassym.c:211: error: storage > size of `MSR_KGSBASEw3' isn't known > *** Error code 1 First, what version of FreeBSD are you trying to compile? Have you recently updated your sources? Second, can you post your complete kernel configuration file? In grepping my CURRENT sources, I find several instances of MSR_KGSBASE under sys, but none with those odd-looking suffixes you're showing. Perhaps something is messed up either in your sources or your kernel config. More info, please! -- Conrad J. Sabatier <conrads@cox.net> -- "In Unix veritas"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040907184811.12372211>