OpenE2K
/
gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

install.texi: Add documentation for installation into tooldirs and with DESTDIR. 

* doc/install.texi: Add documentation for installation into
tooldirs and with DESTDIR.

From-SVN: r62046
This commit is contained in:
Christian Cornelssen 2003-01-29 00:15:43 +01:00 committed by Alexandre Oliva
parent 621d752ac9
commit b42f080f47
2 changed files with 31 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
gcc/ChangeLog
View File

@ -1,5 +1,8 @@
2003-01-28 Christian Cornelssen <ccorn@cs.tu-berlin.de>
* doc/install.texi: Add documentation for installation into
tooldirs and with DESTDIR.
* Makefile.in (ORDINARY_FLAGS_TO_PASS): Also pass DESTDIR.
(install-cpp, uninstall-cpp, installdirs, install-common)
(install-driver, install-info, install-man)

28
gcc/doc/install.texi
View File

@ -1330,6 +1330,34 @@ in @file{@var{libdir}} (normally @file{@var{prefix}/lib}); internal
parts of the compiler in @file{@var{libdir}/gcc-lib}; documentation in
info format in @file{@var{infodir}} (normally @file{@var{prefix}/info}).
When installing cross-compilers, GCC's executables
are not only installed into @file{@var{bindir}}, that
is, @file{@var{exec-prefix}/bin}, but additionally into
@file{@var{exec-prefix}/@var{target-alias}/bin}, if that directory
exists. Typically, such @dfn{tooldirs} hold target-specific
binutils, including assembler and linker.
Installation into a temporary staging area or into a @command{chroot}
jail can be achieved with the command
@example
make DESTDIR=@var{path-to-rootdir} install
@end example
@noindent where @var{path-to-rootdir} is the absolute path of
a directory relative to which all installation paths will be
interpreted. Note that the directory specified by @code{DESTDIR}
need not exist yet; it will be created if necessary.
There is a subtle point with tooldirs and @code{DESTDIR}:
If you relocate a cross-compiler installation with
e.g.@: @samp{DESTDIR=@var{rootdir}}, then the directory
@file{@var{rootdir}/@var{exec-prefix}/@var{target-alias}/bin} will
be filled with duplicated GCC executables only if it already exists,
it will not be created otherwise. This is regarded as a feature,
not as a bug, because it gives slightly more control to the packagers
using the @code{DESTDIR} feature.
If you built a released version of GCC using @samp{make bootstrap} then please
quickly review the build status page for your release, available from
@uref{http://gcc.gnu.org/buildstat.html}.