Date: Sat, 26 Jun 2004 03:03:08 +0200 From: Danny Pansters <danny@ricin.com> To: freebsd-questions@freebsd.org Subject: Re: 2. Try Kernel compiling..makefile stops because of some warnings Message-ID: <200406260303.08547.danny@ricin.com> In-Reply-To: <20040625201938.2a02ffb5.wmoran@potentialtech.com> References: <1088203723.40dcabcbc635b@www.xmail.net> <20040625201938.2a02ffb5.wmoran@potentialtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 26 June 2004 02:19, Bill Moran wrote: > Karim Forsthofer <karim_f@xmail.net> wrote: > > Hello > > > > I tried to compile a new kernel from my 5.1 bsd cd. > > 5.1 is an obsolete, experimental version. If you're new to FreeBSD, you > should be using 4.10. If you want to experiment with the 5.x branch, you > should be using 5.2.1. Many problems that existed in 5.1 have been fixed > in 5.2.1. You're unlikely to get any support for 5.1. That's true. But it supported building my kernels. 5.1 was not unstable or broken. It was less broken than 5.2-REL. Building kernel from cd src should always be supported. This is probably user error. > > "Config" and "make depend" worked well, but "make" stops and > > print out some warnings about unused functions in npx.c (or something > > else). > > This is the old way of building a kernel. You should use "make > buildkernel" as described in the handbook: > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html No. If you have a release from CD with src-sys installed and haven't cvsup'ed anything or don't have src-all fully installed than this *is* the proper way to build a kernel. In fact, it's the only way. There is no such thing as an "old" or a "new" way. These have IMHO unfortunately become the de facto terms but they're not accurate. On my -CURRENT box, when not updating world but merely rebuilding kernel, I normally use the "old" way because it's more straightforward then, starting from editing the conf file. Using make kernel would in that case produce the same of course. > For future reference, it's very difficult to help when problems are > described as "print out some warnings about unused functions in npx.c > (or something else)". If you have questions in the future, you'll get > more helpful answers if you provide the exact error messages. This > document describes how to ask good questions: > http://www.lemis.com/questions.html Yes. Without the actual output all we can do is guess. > > I searched in the newsgroup and found some similar postings to this > > subject > > It seems to me, that the problem appears when the RealTek pci NIC > > device is included in the config file. Someone wrote in the newsgroup, > > that gcc works with the wrong compiler flags, that means that the > > compiler stops at warnings, but he didn`t mention how the solve this > > problem or how to change the flags. > > Any suggestions? With the output we might be able to see if its a warning or an error. > > My Hardware is a d-link nic and the ensoniq 1370 soundcard, the other > > stuff is very common. > > > > The MYKERNEL configfile is attached to this email. I don't see anything wrong with it. How about if you load GENERIC and then kldload your NIC and 137x drivers, does everything work then? It's worth while to note that FreeBSD 5.x generally much more encourages the use of modules rather than compiling in drivers. > > Hope you can help me. Reinstalling to 5.2.1 is a good idea anyhow in the longer run. > > Greetings Karim Cheers, Dan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200406260303.08547.danny>