Compiling kernel module
Hi, I'm trying to get a dummy PCI driver module to compile (code mostly taken from the FreeBSD developer's handbook), and I've run into a problem with a couple of header files. I include the file , and it includes the following two preprocessor directives: #include "device_if.h" #include "bus_if.h" At the moment I'm compiling this module (main source file called fb.c) in my home directory using the following Makefile: -- # Makefile for the skeleton module SRCS = fb.c KMOD = fb .include -- The makefile seems to automatically create an '@' directory linking to /usr/src/sys, but the two headers device_if.h and bus_if.h do not appear in this directory alongside buf.h, so there is a preprocessing error in bus.h. After a bit of diggging, I found that device_if.h and bus_if.h could be found a few directories further in form /usr/src/sys/compile/XXX/.., so my question is, how should I set up my Makefile, etc. to allow me to build my little module? Btw, I can compile a custom kernel no problem, so I don't think my kernel sources have got messed up. thanks, Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: FreeBSD compatibility
It might be easier to recompile them for FreeBSD, instead of running the binaries using Linux emulation. As long as you haven't used any linux-specific system calls, of course. Mostly you shouldn't need to alter your code much / at all. Alex On Thursday 25 July 2002 11:52 am, Daniel Bye wrote: > On Thu, Jul 25, 2002 at 02:12:28PM +0300, Tiago Marques wrote: > > Dear Sirs, > > I'm a user of Linux, and i do some programming for college, some related > > with sockets, processes, and all kinds of linux system programming. > > I've been thinking about moving to FreeBSD but i would like to know if > > the programs i do in Linux will be compatible with FreeBSD. > > I've already installed OpenBSD in another computer but due to some > > problems here i didn't have the time to test those things yet... > > Also, i'm a regular user, but not very experienced in Linux, i just know > > my way around, not much more. Do you think i'll be able to use FreeBSD > > easily or is it more complicated to mantain and admin ? > > Sorry all this questions > > Provided your Linux programs don't make too heavy use of the Linux procfs > (which is significantly different to the BSD implementation), or any of > the extended i386 sys calls, you should be able to run them under FreeBSD, > using the Linux emulation layer. The best thing to do is install FreeBSD, > including the Linux emulation bits and pieces, and try it out. > > (There is code in the base system to support linprocfs, but I have never > had call to use it so cannot offer any help or opinions about it) > > The name FreeBSD refers to the OS as a whole, unlike Linux, which is the > name of the kernel. Therefore, you can consider FreeBSD in the same terms > as RedHat or SuSE - RedHat's OS is _based_on_ a Linux kernel, but the > specific details of the implementation of the rest of the system are down > to the developers who put the thing together. > > Because of this, there is only one FreeBSD "distribution", which you can > rely on being sane from one install to the next - whereas the multitude of > Linux distros are effectively different OSen, and you will find > considerable variation in the specifics. (However, that's not to say that > one RedHat install will be vastly different to the next...) > > Personally, I like FreeBSD's design. I find it to be clean and systematic, > and yes, pretty easy to keep it going smoothly. It also has this list, > which is a truly marvellous source of help and information for those who > can't find what they need elsewhere. Installing new apps is a breeze > using the Ports system (which is so good, that NetBSD and OpenBSD have > adopted it), and the documentation for the base system is, in my opinion, > some of the best written and maintained documentation I have ever come > across. > > But this is all just so much personal opinion. Try it, break it, fix it, > see what you think! > > Dan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
make buildworld fails on 4.7-RELEASE
Hi, I can build a custom kernel fine, but when I execute 'make buildworld' from /usr/src, I get a lot of errors relating to libgroff (see bellow). I have all the (4.7-RELEASE) source packages installed. Does anyone have any idea what the problem might be? Would be really grateful for any help, Alex /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/cmap.cc:25: cmap.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/cset.cc:25: cset.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/device.cc:22: device.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/device.cc:23: defs.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/errarg.cc:23: errarg.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/error.cc:24: errarg.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/error.cc:25: error.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/font.cc:28: errarg.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/font.cc:29: error.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/font.cc:30: cset.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/font.cc:31: font.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/font.cc:32: lib.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/fontfile.cc:26: font.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/fontfile.cc:27: lib.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/fontfile.cc:28: searchpath.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/fontfile.cc:29: device.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/fontfile.cc:30: defs.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/htmlindicate.cc:24: nonposix.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/htmlindicate.cc:25: stringclass.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/htmlindicate.cc:26: html-strings.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/lf.cc:23: cset.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/lf.cc:24: stringclass.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/macropath.cc:21: lib.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/macropath.cc:22: searchpath.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/macropath.cc:23: macropath.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/macropath.cc:24: defs.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/nametoindex.cc:26: lib.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/nametoindex.cc:27: errarg.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/nametoindex.cc:28: error.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/nametoindex.cc:29: font.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/nametoindex.cc:30: ptable.h: No such file or directory /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/new.cc:
Re: nVidia drivers w/ 4.7-RELEASE
Interesting to see that other people found they worked fine with RELEASE. I had to update my system to STABLE before GLX would work, although I had no problems otherwise. Also, GLX would only work with an XFree86 installed from ports, not with one installed from the FreeBSD binaries on xfree86.org (my original X installation was done befroe XFree86 4 was in ports). Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
