2001-01-24 00:31:17 +00:00
|
|
|
<sect1 id="ch02-install">
|
|
|
|
<title>How to install the software</title>
|
|
|
|
|
|
|
|
<para>
|
2001-03-23 02:56:31 +00:00
|
|
|
Before you can actually start doing something with a package, you need
|
2001-03-16 18:06:46 +00:00
|
|
|
to unpack it first. Often the package files are tar'ed and
|
2001-04-13 00:41:40 +01:00
|
|
|
gzip'ed or bzip2'ed. I'm not going to write down every time how to
|
|
|
|
unpack an archive. I will explain how to do that once, in this
|
|
|
|
section.
|
2001-01-24 00:31:17 +00:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
To start with, change to the $LFS/usr/src directory by running:
|
|
|
|
</para>
|
|
|
|
|
2001-07-06 16:25:48 +01:00
|
|
|
<para>
|
|
|
|
<screen>
|
|
|
|
<userinput>cd $LFS/usr/src</userinput>
|
|
|
|
</screen>
|
|
|
|
</para>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
|
|
|
<para>
|
2001-03-16 18:06:46 +00:00
|
|
|
If a file is tar'ed and gzip'ed, it is unpacked by
|
2001-01-24 00:31:17 +00:00
|
|
|
running either one of the following two commands, depending on the
|
2001-03-23 02:56:31 +00:00
|
|
|
filename:
|
2001-01-24 00:31:17 +00:00
|
|
|
</para>
|
|
|
|
|
2001-07-06 16:25:48 +01:00
|
|
|
<para>
|
|
|
|
<screen>
|
|
|
|
<userinput>tar xvzf filename.tar.gz</userinput>
|
|
|
|
<userinput>tar xvzf filename.tgz</userinput>
|
|
|
|
</screen>
|
|
|
|
</para>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
|
|
|
|
|
|
|
<para>
|
2001-03-16 18:06:46 +00:00
|
|
|
If a file is tar'ed and bzip2'ed, it is unpacked by
|
2001-01-24 00:31:17 +00:00
|
|
|
running:
|
|
|
|
</para>
|
|
|
|
|
2001-07-06 16:25:48 +01:00
|
|
|
<para>
|
|
|
|
<screen>
|
|
|
|
<userinput>bzcat filename.tar.bz2 | tar xv</userinput>
|
|
|
|
</screen>
|
|
|
|
</para>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
|
|
|
<para>
|
|
|
|
Some tar programs (most of them nowadays but not all of them) are
|
|
|
|
slightly modified to be able to use bzip2 files directly using either
|
2001-03-22 03:27:52 +00:00
|
|
|
the I or the y tar parameter, which works the same as the z tar parameter
|
2001-03-23 02:56:31 +00:00
|
|
|
to handle gzip archives. The above construction works no matter how
|
|
|
|
your host system decided to patch bzip2.
|
2001-01-24 00:31:17 +00:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2001-03-16 18:06:46 +00:00
|
|
|
If a file is just tar'ed, it is unpacked by running:
|
2001-01-24 00:31:17 +00:00
|
|
|
</para>
|
|
|
|
|
2001-07-06 16:25:48 +01:00
|
|
|
<para>
|
|
|
|
<screen>
|
|
|
|
<userinput>tar xvf filename.tar</userinput>
|
|
|
|
</screen>
|
|
|
|
</para>
|
2001-01-24 00:31:17 +00:00
|
|
|
|
|
|
|
<para>
|
2001-04-25 22:21:54 +01:00
|
|
|
When an archive is unpacked, a new directory will be created under the
|
2001-04-13 00:28:53 +01:00
|
|
|
current directory (and this book assumes that the archives are unpacked
|
2001-03-23 02:56:31 +00:00
|
|
|
under the $LFS/usr/src directory). Please enter that new directory
|
|
|
|
before continuing with the installation instructions. Again, every time
|
|
|
|
this book is going to install a package, it's up to you to unpack the source
|
|
|
|
archive and cd into the newly created directory.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
From time to time you will be dealing with single files such as patch
|
|
|
|
files. These files are generally gzip'ed or bzip2'ed. Before such files
|
|
|
|
can be used they need to be uncompressed first.
|
2001-01-24 00:31:17 +00:00
|
|
|
</para>
|
|
|
|
|
2001-02-23 17:56:03 +00:00
|
|
|
<para>
|
2001-03-22 03:27:52 +00:00
|
|
|
If a file is gzip'ed, it is unpacked by running:
|
2001-02-23 17:56:03 +00:00
|
|
|
</para>
|
|
|
|
|
2001-07-06 16:25:48 +01:00
|
|
|
<para>
|
|
|
|
<screen>
|
|
|
|
<userinput>gunzip filename.gz</userinput>
|
|
|
|
</screen>
|
|
|
|
</para>
|
2001-02-23 17:56:03 +00:00
|
|
|
|
2001-03-23 02:56:31 +00:00
|
|
|
<para>
|
|
|
|
If a file is bzip2'ed, it is unpacked by running:
|
2001-03-23 03:05:35 +00:00
|
|
|
</para>
|
2001-03-23 02:56:31 +00:00
|
|
|
|
2001-07-06 16:25:48 +01:00
|
|
|
<para>
|
|
|
|
<screen>
|
|
|
|
<userinput>bunzip2 filename.bz2</userinput>
|
|
|
|
</screen>
|
|
|
|
</para>
|
2001-03-23 02:56:31 +00:00
|
|
|
|
2001-01-24 00:31:17 +00:00
|
|
|
<para>
|
2001-04-13 00:41:40 +01:00
|
|
|
After a package has been installed, two things can be done with it:
|
2001-03-22 03:27:52 +00:00
|
|
|
either the directory that contains the sources can be deleted,
|
2001-04-13 00:28:53 +01:00
|
|
|
or it can be kept. If it is kept, that's fine with me, but if the
|
2001-03-23 02:56:31 +00:00
|
|
|
same package is needed again in a later chapter, the directory
|
|
|
|
needs to be deleted first before using it again. If this is not done,
|
|
|
|
you might end up in trouble because old settings will be used (settings
|
2001-04-13 00:28:53 +01:00
|
|
|
that apply to the host system but which don't always apply to
|
2001-03-23 02:56:31 +00:00
|
|
|
the LFS system). Doing a simple make clean or make distclean does not
|
|
|
|
always guarantee a totally clean source tree.
|
2001-01-24 00:31:17 +00:00
|
|
|
</para>
|
|
|
|
|
2001-04-13 00:41:40 +01:00
|
|
|
<para>
|
|
|
|
So, save yourself a lot of hassle and just remove the source directory
|
|
|
|
immediately after you have installed it.
|
|
|
|
</para>
|
|
|
|
|
2001-01-24 00:31:17 +00:00
|
|
|
<para>
|
2001-04-13 00:28:53 +01:00
|
|
|
There is one exception to that rule: don't remove the Linux kernel source
|
2001-01-24 00:31:17 +00:00
|
|
|
tree. A lot of programs need the kernel headers, so that's the only
|
2001-04-13 00:41:40 +01:00
|
|
|
directory that should not be removed, unless no package is to be compiled
|
2001-03-16 18:06:46 +00:00
|
|
|
anymore.
|
2001-01-24 00:31:17 +00:00
|
|
|
</para>
|
|
|
|
|
|
|
|
</sect1>
|
|
|
|
|