CDA SC510 Guia do Utilizador Página 39

  • Descarregar
  • Adicionar aos meus manuais
  • Imprimir
Vista de página 38
D2.1.4 IST-033576
% s e t e n v PATH ${PATH } : PREFIX / b i n
% s e t e n v MANPATH ${MANPATH} : PR EFIX / man
% s e t e n v LD_LIBRARY_PATH $ {LD_LIBRARY_PATH } : PREFIX / l i b
A.2 Uninstalling BLCR
If you preserve the BLCR build tree, then there is a standard uninstall make target
available to remove the files copied by the install target.
A.3 Making RPMs from the BLCR sources
An alternate way to install BLCR is to build a binary RPM for your system, which
you can then install. This has certain advantages (such as making upgrading eas-
ier, especially if you maintain BLCR on multiple systems).
A.3.1 Building binary RPMs from the source tarball
Once you’ve configured BLCR with any options your system requires, the sim-
plest method for building RPMs is to just
% make rpms
If successful, the new RPM packages will be in the rpm/RPMS subdirectory of
the build tree. The resulting packages will be for whatever kernel you configured
for.
A.3.2 Building a binary RPM from source RPMS
You may also with start from a source RPM (with a .src.rpm suffix) rather than
the .tar.gz version of the BLCR distribution. Source RPMs are available on our
website. These source RPMs are configured to build for the running kernel, with
–prefix=/usr and to configure with –enable-multilib on 64-bit platforms. Alter-
natively, the make rpms step above will create a source RPM in the rpm/SRPMS
subdirectory of the build tree, valid for the configured kernel.
If building as root, built RPMs will be placed in a subdirectory of /usr/src/red-
hat/RPMS. However, if you are not root, you may need to see this page at IBM
for information on configuring an output location before proceeding. Personally,
we prefer not to build as root.
To build binary RPMs from the source RPM, use
37/49 XtreemOS–Integrated Project
Vista de página 38
1 2 ... 34 35 36 37 38 39 40 41 42 43 44 ... 50 51

Comentários a estes Manuais

Sem comentários