home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!spool.mu.edu!umn.edu!csus.edu!csusac!citrus!ianj
- From: ianj@citrus.SAC.CA.US ( Ian Justman )
- Subject: Re: Can't make 0.98pl6 !
- References: <1992Dec12.191734.50021@ccvax.ucd.ie>
- Organization: Citrus Grove Public Access ( 916 ) 381-5822 Sacramento CA. USA
- Date: Mon, 14 Dec 1992 01:07:10 GMT
- X-Newsreader: Tin 1.1 PL4
- Message-ID: <Bz85s1.12zJ@citrus.SAC.CA.US>
- Lines: 30
-
- h235_003@ccvax.ucd.ie (ARE WE HAVING FUN YET) writes:
- :
- : I'm having trouble making the 0.98pl6 kernel - everything goes fine until
- : it gets to linking things, then I get a load of Undefined symbols - mostly
- : _put_fs_long, _put_fs_byte, and things like _set_bit and _clear_bit.
- :
- : How do I get this to compile ??? (I have the SLS 0.98 distribution with
- : the 2.2.2d gcc libs)
-
- The compiler that came with your system will work just fine. It does for
- me. Anyway, it sounds like you have a few files not being included (or
- more appropriate, the appropriate files are not being included). This
- is mainly because you need symbolic links in the /usr/include directory
- which point to /usr/src/linux/include/linux and /usr/src/linux/include/asm
- named linux and asm respectively. Then the kernel will compile properly.
-
- One note, if you already have directories called /usr/include/linux and
- /usr/include/asm, and you don't want to erase the stuff in those director-
- ies, use mv to rename them to something like "linux_bak" and "asm_bak"
- respectively before applying the links.
-
- Query: I myself have made said symbolic links. I figure since now I'm using
- pl6, should I keep the linux and asm links pointed to the directories con-
- taining the Linux include files to guarantee compatiblity with pl6. Is it
- wise to operate under that philosophy?
-
- Thanks for any pearls of wisdom.
-
- --
- Born to void warranties! ianj@ijpc.UUCP
-