On 16/04/15 05:45, Glen Gunselman wrote:
I am researching PCP (and friends) as a replacement for Orca/SE Toolkit.
Welcome, Glen.
...
$ su root
# make install
This is really not the best recipe ... Makepkgs is preferred and will
create rpms for your environment (and suitable packages for other
environments) ... from the INSTALL file (as recently updated) ...
== B. Building from source
0. Preliminaries
The PCP code base is targeted for many different operating
systems and many different combinations of related packages,
so a little planning is needed before launching into a build
from source.
Package dependencies come in several flavours:
(a) hard build dependencies - without these PCP cannot be
build from source, and the build will fail in various
ways at the compilation or packaging stages, e.g. gmake,
autoconf, flex, bison, ...;
(b) optional build dependences - if these components are not
installed the build will work, but the resultant packages
may be missing some features or entire applications, e.g.
extended authentication, secure connections, service
discovery, pmwebd, ...;
(c) QA dependencies - you can ignore these unless you want to
run the (extensive) PCP QA suite.
It is strongly recommended that you run the script:
$ qa/admin/check-vm
and review the output before commencing a build.
1. Configure, build and install the package
The pcp package uses autoconf/configure and expects a GNU build
environment (your platform must at least have gmake).
If you just want to spin a .RPM, .DEB, .DMG, .EXE and/or tar
file, use the Makepkgs script in the top level directory.
This will configure and build the package for your platform and
leave binary and src packages in the build/<pkg-type> directory.
It will also leave binary and source tar file in the build/tar
directory.
$ ./Makepkgs --verbose
|