From: rafal@utstat.uucp (Rafal Kustra (summer student))
Subject: Re: gcc install doc
Organization: University of Toronto, Dept. of Statistics
Date: Wed, 9 Sep 1992 14:23:52 GMT

In article <1597@lysator.liu.se>  writes:
>
>Regarding the gcc install files.  I have read the README, as well as
>all releasenotes, and the FAQ.  Most of the contents seem directed
>to unix gurus, and treats mainly compiler options or if it is ANSI
>compliant.  I just want a gcc so I can compile and install programs
>I find in the archives, and maybe later on adjust programs I have
>slightly.  A C compiler seems to be essential on a unix system,
>that's why I want it.  I might get the fortran to c converter,
>because I have written short programs in fortran before.  I am NOT a
>programmer.  I DO NOT know C.  I do not have the time to learn all
>about C now. If I cannot get gcc to work without much perspiration, I
>will just kick it out - and never learn or use C...    Most of the
>people who have replied to me have just said "read the README!".  But
>the README does NOT answer the questions I have - if it does, please
>point i out to me, and I will apologize for my stupidity.
>
>By the way, I managed to boot and install linux without much trouble.
>I managed to get mtools on line, and after that emacs, and ka9q.
>Thanks to all those kind souls who provided those packages,
>especially to Jim Winstead, as I had very few problems in that
>installation!  This should mean I am not a completely stupid asshole?
>
>What the gcc README does not tell me:
>
>-  does not give me any information on what to do about the fact that
>   linux truncates filenames longer than 14 characters.  The install
>   script does not seem to complain about it, when I tested it, now.
>   But there should definetly be a remark there about this.
No, you should'n worry about it if you get your files
onto unix in their original names (minus extra chars).
Kernel takes care of that when script asks for big f-name
it truncates it the same way as it did when you untar it
there. Problem may arise if you go thru DOS. Then you
must take care that upon getting it to Linux you should
get them back to original names (or first 14 chars of
that).
>-  where files will end up (new directories, plus most important what
Thirst You must (should) have gcc 2.2.2 instaled.
As far as my memory serves me:
1) include files will go into /usr/inlude plus subdirs.
2.2.2 include will be erased. You should take care about
setjmp.h as described in release (or FAQ) note.
2)libraries will go to /usr/lib/gcc-lib/i386-linux/2.2.2d
You should also get include, jump and shared subdirs
there.
files from binutils go into /usr/bin
>   files go into existing directories).
>-  how to uninstall gcc
???
>-  what procedures the install script actually performs:    simply
>   untar all archives, or does it do something else?
It untars it puts it into rights places, removes old
compiler( ie its includes and binaries) links
/usr/src/linux/include with /usr/include/linux, creates
/usr/lib/gcc-lib/i386-linux/2.2.2d/specs containing
ver #. 
>-  does the install script actually check that all files are where
>   they should, that it works?
No, I dont think so. It checks for dirs. Some of them
should'nt be there (like /usr/lib/gcc-lib/i386-linux/2.2.2d) 
so it will fail on its existance with error message. It
doesn't check if files are in right places 'cause it puts
them there. But you should read all docs (readme, FAQ and
all 2.xx realease notes) couple of times before
installing it. You must have .97plx sources on line and
you should have gcc 2.2.2 installed.(you will need it
anyway).
>-  I don't understand the final remarks in the install file.
>
>   Please get rid of all the -"nostdinc -I" from the Makefiles in
>   kernel sources and then do a fresh "make dep".
>
>   What is -nostdinc ???   make dep  on my linux just gives me
>   make: command not found
-nostdinc is a flag that tells compiler (actually a
preprocessor) not to look in std include dirs (defined
inside compiler) but in dirs specifide on command line.
You should remove it from Makefiles (actually only one in
/usr/src/linux) because include files from compiler and
the kernel are now consistent. 
Make is a utility that automates compiling large (and
small) projects which come in number of source files. You
should have it in /bin or /usr/bin on root disk. If not
look for it in tsx-11.mit.edu (pub/linux/binaries/usr.bin
I think).
Make reads Makefile for instructions. You should learn
how to use it even if you dont plan on learning C.Almost
all software in Unix world comes in sources with
makefiles. Read man make on your Unix machine.
>-  where I find gdb
Should be on tsx-11. Maybe you can wait. Someone is
getting ver 4.6 to compile.
>-  where and how do I find a "make" to install
>-  what do I have to do if I decide to move my kernel source to
>   another directory
why would you? But then it is no problem. Just mv it and
create a symlink form /your kernel src/include to
/usr/include/linux if you already installed gcc 2.2.2d or
tell instal.2.x right directory. Also you will have to
tell it to ps package - read readme there.
>
>I do not want to have to become a unix guru just to use linux.
>Then I could as well do something productive, like program an old IBM
>360 with punch cards :-)
>
>This was not a flame, just a comment.  I appreciate that HJ has spent
>effort on the gcc compiler.  I simply didn't get it working anyway.
>I volunteer to improve the install doc, IF AND ONLY IF, I get to the
>point that understand (or think I understand) how it works.

				Rafal
-- 
/|| Numbers exist only in our minds. There is no physical entity that
 ||_is_ number 1. If there were, 1 would be in a place of honor in 
 || some great museum of science, and past it would file a steady
==== stream of mathematicians gazing at 1 in wonder and awe.
Newsgroups: comp.os.linux