public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* Minor suggestion on docs
@ 2001-10-28 11:20 Harry Putnam
  0 siblings, 0 replies; only message in thread
From: Harry Putnam @ 2001-10-28 11:20 UTC (permalink / raw)
  To: gcc-help

I may be the only dope around who was confused by the recommended
proceedure to build gcc.  But I am guessing there may be quite a few
like me.  If that is true and maintainers find this description
accurate then I have a suggestion.

I suggest that this simplified outline appear near the top of a text
file named gcc-VERSION/INSTALL.  And that the current package
directory, gcc-VERSION/INSTALL/, be renamed to gcc-VERSION/install/.
This would be in keeping with what is sort of standard text file found
in gnu gnu packages: package-version/INSTALL

And further that the sample be included near the top of
gcc-VERSION/install/configure.html. Possibly
gcc-VERSION/install/build.html as well.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
A sample simplified proceedure to download, build and install current
GCC is summarized below. Most users will need to be logged in as root
for at least the last `make install' command.

This is a simplified summary only.  Details can be found in the
`install/' directory of an unpacked gcc package, in the various
gcc-VERSION/install/*.html files. Or the online documentation at:
http://gcc.gnu.org/install/

Sample outline proceedure:
1:
    ======================================== 
    Present working directory (pwd) is: /usr/local
 
    Make a directory to store tar packages or use an existing directory:
     $ mkdir source_tar_packages
     $ cd source_tar_packages

    Use ftp to download current released gcc to this directory
    example using ncftp: 
     $ ncftp ftp://ftp.gnu.org/gnu/gcc/gcc-3.0.2/gcc-3.0.2.tar.gz
    ========================================
2.
    ========================================
     Present working directory  (pwd) is: /usr/local/source_tar_packages
     Move up one level to /usr/local
      $ cd ..

     Unpack gcc-3.0.2.tar.gz here
      $ tar xzvf source_tar_packages/gcc-3.0.2.tar.gz
     
     Create a directory to build gcc
      $ mkdir gcc-3.0.2-build
     
    A directory listing should now show at least these directories
    
      $ ls
        gcc-3.0.2           <== unpacked gcc souce directory
        gcc-3.0.2-build     <== empty directory where build will take place
        source_tar_packages <== where you downloaded gcc-3.0.2.tar.g
    ========================================
3.
    ========================================
    Present working directory is /usr/local
    
    Move to build directory.  We recommend building GCC from a directory
    outside the unpacked source directory as shown above 
     $ cd gcc-3.0.2-build
    ========================================
 4.
    ========================================
    Start the build proceedure:
    Present woring directory is /usr/local/gcc-3.0.2-build

    Call `configure':
     $ ../gcc-3.0.2/configure [options]

    Call `make bootstrap'
     $ make bootstrap
    
    Call `make check'
     $ make check
    
    Call `make install'
     $ make install
    ========================================

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2001-10-28 11:20 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-10-28 11:20 Minor suggestion on docs Harry Putnam

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).