Date: Sat, 20 Jan 2007 10:48:30 -0500 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: "James Hein" <jhein_98@swbell.net> Cc: freebsd-questions@freebsd.org Subject: Re: Problems with custom kernel fbsd 6.2 Message-ID: <44fya51yy9.fsf@Lowell-Desk.lan> In-Reply-To: <000501c73c3a$f5036a80$030210ac@ENKITE.local> (James Hein's message of "Fri, 19 Jan 2007 20:30:30 -0600") References: <000501c73c3a$f5036a80$030210ac@ENKITE.local>
next in thread | previous in thread | raw e-mail | index | archive | help
"James Hein" <jhein_98@swbell.net> writes: > Thanks for trying to help, but that didn't seem to be it. It did > the same thing, with the same error. Can you think of anything else > that may be wrong? I'm considering rebuilding it again with > debugging on, and using script to output it to a log. It has to be > something in my config though, simply because the only thing > different between my generic and custom compiles is the config > file. I don't know how to make it not compile certain things with > make, which makes my compile take awhile on it because of its > specs. I've read something on how to do that, I just don't 'know' > how to do it yet. Well, one quick look at your configuration also shows me that umass is in there but not scbus or da, which the comment on umass shows won't work. However, the basic approach you should use is to go back to a copy of the GENERIC kernel and start adding your changes a few at a time, so that when the build breaks, you will be easily able to figure out exactly which change was the problem. Also, you might want to look at the "How to get the best results from the FreeBSD-questions mailing list" article in the FreeBSD documentation. Its author frequently posts it to this list. It will give you valuable hints about how to help us to help you. Good luck.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44fya51yy9.fsf>