home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cis.ohio-state.edu!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!chester.ksu.ksu.edu!news
- From: probreak@chester.ksu.ksu.edu (James Michael Chacon)
- Newsgroups: comp.os.linux
- Subject: Re: gcc install: files missing
- Date: 4 Sep 1992 01:14:38 -0500
- Organization: Kansas State University
- Lines: 49
- Message-ID: <186usfINNb5i@chester.ksu.ksu.edu>
- References: <1573@lysator.liu.se>
- NNTP-Posting-Host: chester.ksu.ksu.edu
-
- lien@lysator.liu.se (Jan Lien) writes:
-
-
- >I recently tried installing gcc 2.2.2d and succeded to get the script
- >running after a while. Linux does not support more than 14 char
- >filenames, so one has to change the install script to shorter
- >names, and rename the files.
-
- >However, I am now unable to compile programs. When I tried one
- >program (diskbackup.c) from the archives, I get
-
- > In file included from diskbackup.c:6:
- > /usr/include/sys/types.h:1: linux/types.h: No such file or directory
- > In file included from /usr/include/sys/stat.h:5, from diskbackup.c:7:
- > /usr/include/sys/types.h:1: linux/types.h: No such file or directory
- > In file included from diskbackup.c:7:
- > /usr/include/sys/stat.h:8: linux/stat.h: No such file or directory
- > In file included from /usr/include/fcntl.h:5, from diskbackup.c:8:
- > /usr/include/sys/types.h:1: linux/types.h: No such file or directory
- > In file included from diskbackup.c:8:
- > /usr/include/fcntl.h:6: linux/fcntl.h: No such file or directory
-
- >The statements
- > #include <linux/types.h> in /usr/include/sys/types.h
- > #include <linux/stat.h> in /usr/include/sys/stat.h
- >and #include <linux/fcntl.h> in /usr/include/fcntl.h
- >apparantly reference files I do not have. Where do I find them - but
- >even more important is maybe : What other files may be missing?
- >Does not the install script really check everything? How can I check
- >that my installation is complete?
-
- You really shouldn'y have to change the install script at all to get it
- to work. All the files for gcc are unique out to 14 chars, so just name them
- what they should be with a mv, and the kernel will strip off whatever it finds
- after 14. This won't cause a problem with install as it does the same thing
- when looking for them. Also, did you read the README files????
- I had no problem installing gcc after I had everything the README stated.
- You need to have the linux source code on line, and it has to be 0.97
- I believe. If you don't have it everything will fail, because the symlinks
- for the /usr/src/linux/include/linux aren't made to /usr/include/linux
-
- Please, as H.J. will probably say: READ EVERYTHING FIRST
-
-
-
- ----------------------- ---------------------------
- -Oh the joy of finding- James Chacon -probreak@matt.ksu.ksu.edu-
- -That last pizza slice- ---------------------------
- ----------------------- ---------------------------
-