OpenCores
URL https://opencores.org/ocsvn/scarts/scarts/trunk

Subversion Repositories scarts

[/] [scarts/] [trunk/] [toolchain/] [scarts-gcc/] [gcc-4.1.1/] [INSTALL/] [finalinstall.html] - Blame information for rev 22

Go to most recent revision | Details | Compare with Previous | View Log

Line No. Rev Author Line
1 13 jlechner
<html lang="en">
2
<head>
3
<title>Installing GCC: Final installation</title>
4
<meta http-equiv="Content-Type" content="text/html">
5
<meta name="description" content="Installing GCC: Final installation">
6
<meta name="generator" content="makeinfo 4.8">
7
<link title="Top" rel="top" href="#Top">
8
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
9
<!--
10
Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
11
1999, 2000, 2001, 2002, 2003, 2004, 2005 Free Software Foundation, Inc.
12
 
13
   Permission is granted to copy, distribute and/or modify this document
14
under the terms of the GNU Free Documentation License, Version 1.2 or
15
any later version published by the Free Software Foundation; with no
16
Invariant Sections, the Front-Cover texts being (a) (see below), and
17
with the Back-Cover Texts being (b) (see below).  A copy of the
18
license is included in the section entitled "GNU Free Documentation License".
19
 
20
(a) The FSF's Front-Cover Text is:
21
 
22
     A GNU Manual
23
 
24
(b) The FSF's Back-Cover Text is:
25
 
26
     You have freedom to copy and modify this GNU Manual, like GNU
27
     software.  Copies published by the Free Software Foundation raise
28
     funds for GNU development.-->
29
<meta http-equiv="Content-Style-Type" content="text/css">
30
<style type="text/css"><!--
31
  pre.display { font-family:inherit }
32
  pre.format  { font-family:inherit }
33
  pre.smalldisplay { font-family:inherit; font-size:smaller }
34
  pre.smallformat  { font-family:inherit; font-size:smaller }
35
  pre.smallexample { font-size:smaller }
36
  pre.smalllisp    { font-size:smaller }
37
  span.sc    { font-variant:small-caps }
38
  span.roman { font-family:serif; font-weight:normal; }
39
  span.sansserif { font-family:sans-serif; font-weight:normal; }
40
--></style>
41
</head>
42
<body>
43
<h1 class="settitle">Installing GCC: Final installation</h1>
44
Now that GCC has been built (and optionally tested), you can install it with
45
<pre class="smallexample">     cd <var>objdir</var>; make install
46
</pre>
47
   <p>We strongly recommend to install into a target directory where there is
48
no previous version of GCC present.
49
 
50
   <p>That step completes the installation of GCC; user level binaries can
51
be found in <samp><var>prefix</var><span class="file">/bin</span></samp> where <var>prefix</var> is the value
52
you specified with the <samp><span class="option">--prefix</span></samp> to configure (or
53
<samp><span class="file">/usr/local</span></samp> by default).  (If you specified <samp><span class="option">--bindir</span></samp>,
54
that directory will be used instead; otherwise, if you specified
55
<samp><span class="option">--exec-prefix</span></samp>, <samp><var>exec-prefix</var><span class="file">/bin</span></samp> will be used.)
56
Headers for the C++ and Java libraries are installed in
57
<samp><var>prefix</var><span class="file">/include</span></samp>; libraries in <samp><var>libdir</var></samp>
58
(normally <samp><var>prefix</var><span class="file">/lib</span></samp>); internal parts of the compiler in
59
<samp><var>libdir</var><span class="file">/gcc</span></samp> and <samp><var>libexecdir</var><span class="file">/gcc</span></samp>; documentation
60
in info format in <samp><var>infodir</var></samp> (normally
61
<samp><var>prefix</var><span class="file">/info</span></samp>).
62
 
63
   <p>When installing cross-compilers, GCC's executables
64
are not only installed into <samp><var>bindir</var></samp>, that
65
is, <samp><var>exec-prefix</var><span class="file">/bin</span></samp>, but additionally into
66
<samp><var>exec-prefix</var><span class="file">/</span><var>target-alias</var><span class="file">/bin</span></samp>, if that directory
67
exists.  Typically, such <dfn>tooldirs</dfn> hold target-specific
68
binutils, including assembler and linker.
69
 
70
   <p>Installation into a temporary staging area or into a <samp><span class="command">chroot</span></samp>
71
jail can be achieved with the command
72
 
73
<pre class="smallexample">     make DESTDIR=<var>path-to-rootdir</var> install
74
</pre>
75
   <p class="noindent">where <var>path-to-rootdir</var> is the absolute path of
76
a directory relative to which all installation paths will be
77
interpreted.  Note that the directory specified by <code>DESTDIR</code>
78
need not exist yet; it will be created if necessary.
79
 
80
   <p>There is a subtle point with tooldirs and <code>DESTDIR</code>:
81
If you relocate a cross-compiler installation with
82
e.g. `<samp><span class="samp">DESTDIR=</span><var>rootdir</var></samp>', then the directory
83
<samp><var>rootdir</var><span class="file">/</span><var>exec-prefix</var><span class="file">/</span><var>target-alias</var><span class="file">/bin</span></samp> will
84
be filled with duplicated GCC executables only if it already exists,
85
it will not be created otherwise.  This is regarded as a feature,
86
not as a bug, because it gives slightly more control to the packagers
87
using the <code>DESTDIR</code> feature.
88
 
89
   <p>If you built a released version of GCC using `<samp><span class="samp">make bootstrap</span></samp>' then please
90
quickly review the build status page for your release, available from
91
<a href="http://gcc.gnu.org/buildstat.html">http://gcc.gnu.org/buildstat.html</a>.
92
If your system is not listed for the version of GCC that you built,
93
send a note to
94
<a href="mailto:gcc@gcc.gnu.org">gcc@gcc.gnu.org</a> indicating
95
that you successfully built and installed GCC.
96
Include the following information:
97
 
98
     <ul>
99
<li>Output from running <samp><var>srcdir</var><span class="file">/config.guess</span></samp>.  Do not send
100
that file itself, just the one-line output from running it.
101
 
102
     <li>The output of `<samp><span class="samp">gcc -v</span></samp>' for your newly installed <samp><span class="command">gcc</span></samp>.
103
This tells us which version of GCC you built and the options you passed to
104
configure.
105
 
106
     <li>Whether you enabled all languages or a subset of them.  If you used a
107
full distribution then this information is part of the configure
108
options in the output of `<samp><span class="samp">gcc -v</span></samp>', but if you downloaded the
109
&ldquo;core&rdquo; compiler plus additional front ends then it isn't apparent
110
which ones you built unless you tell us about it.
111
 
112
     <li>If the build was for GNU/Linux, also include:
113
          <ul>
114
<li>The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
115
this information should be available from <samp><span class="file">/etc/issue</span></samp>.
116
 
117
          <li>The version of the Linux kernel, available from `<samp><span class="samp">uname --version</span></samp>'
118
or `<samp><span class="samp">uname -a</span></samp>'.
119
 
120
          <li>The version of glibc you used; for RPM-based systems like Red Hat,
121
Mandrake, and SuSE type `<samp><span class="samp">rpm -q glibc</span></samp>' to get the glibc version,
122
and on systems like Debian and Progeny use `<samp><span class="samp">dpkg -l libc6</span></samp>'.
123
</ul>
124
     For other systems, you can include similar information if you think it is
125
relevant.
126
 
127
     <li>Any other information that you think would be useful to people building
128
GCC on the same configuration.  The new entry in the build status list
129
will include a link to the archived copy of your message.
130
</ul>
131
 
132
   <p>We'd also like to know if the
133
<a href="specific.html">host/target specific installation notes</a>
134
didn't include your host/target information or if that information is
135
incomplete or out of date.  Send a note to
136
<a href="mailto:gcc@gcc.gnu.org">gcc@gcc.gnu.org</a> detailing how the information should be changed.
137
 
138
   <p>If you find a bug, please report it following the
139
<a href="../bugs.html">bug reporting guidelines</a>.
140
 
141
   <p>If you want to print the GCC manuals, do `<samp><span class="samp">cd </span><var>objdir</var><span class="samp">; make
142
dvi</span></samp>'.  You will need to have <samp><span class="command">texi2dvi</span></samp> (version at least 4.2)
143
and TeX installed.  This creates a number of <samp><span class="file">.dvi</span></samp> files in
144
subdirectories of <samp><var>objdir</var></samp>; these may be converted for
145
printing with programs such as <samp><span class="command">dvips</span></samp>.  You can also
146
<a href="http://www.gnu.org/order/order.html">buy printed manuals from the Free Software Foundation</a>, though such manuals may not be for the most
147
recent version of GCC.
148
 
149
   <p>If you would like to generate online HTML documentation, do `<samp><span class="samp">cd
150
</span><var>objdir</var><span class="samp">; make html</span></samp>' and HTML will be generated for the gcc manuals in
151
<samp><var>objdir</var><span class="file">/gcc/HTML</span></samp>.
152
 
153
   <p><hr />
154
<p><a href="./index.html">Return to the GCC Installation page</a>
155
 
156
<!-- ***Binaries**************************************************************** -->
157
<!-- ***Specific**************************************************************** -->
158
<!-- ***Old documentation****************************************************** -->
159
<!-- ***GFDL******************************************************************** -->
160
<!-- *************************************************************************** -->
161
<!-- Part 6 The End of the Document -->
162
</body></html>
163
 

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.