Print this page
8998 depcheck is useless and should be removed
8992 checkproto is useless and can be deleted
8991 pmodes is useless and can be deleted
8990 /opt/onbld/gk is useless
@@ -23,28 +23,19 @@
This directory contains the tools used to do a full build of the
OS/Net workspace. They usually live in the /opt/onbld directory on build
machines. From here, 'make install' will build and install the tools
-in $ROOT/opt/onbld. If you like, 'make pkg' will build the SUNWonbld
-package in $(PKGARCHIVE). Installing that package will populate the
-/opt/onbld directory, and create a root account for building called 'gk',
-which uses csh and has a home directory of /opt/onbld/gk. You can
-use this account to do full builds with 'nightly'. You don't have to,
-but the 'gk' account has the path setup properly, has a .make.machines
-file for dmake, and has a .login that sets up for dmake.
+in $ROOT/opt/onbld.
Layout of /opt/onbld
--------------------
/opt/onbld/etc/abi
contains Solaris ABI database (ABI_*.db) and exceptions
for ABI Auditing tool (interface_check, interface_cmp).
-/opt/onbld/gk
- gk account's home directory.
-
/opt/onbld/bin
basic bin directory - contains scripts.
/opt/onbld/bin/${MACH}
architecture-specific bin directory for binaries.
@@ -99,15 +90,10 @@
the -o option to simplify the output for diffing with previous
build results. It also uses the -i option to obtain NEEDED and RUNPATH
entries, which help detect changes in software dependencies and makes
sure objects don't have any strange runpaths like /opt/SUNWspro/lib.
-checkproto
- Runs protocmp and protolist on a workspace (or uses the environment
- variable CODEMGR_WS to determine the workspace). Checks the proto area
- against the packages.
-
codereview
Given two filenames, creates a postscript file with the file
differences highlighted.
codesign
@@ -140,18 +126,10 @@
Decode and display CTF data stored in a raw file or in an ELF file.
ctfmerge
Merge the CTF data from one or more object files.
-depcheck
- A tool to try an assess the dependencies of executables. This tool
- is not a definitive dependency check, but it does use "strings" and
- "ldd" to gather as much information as it can. The dependency check
- tool can handle filenames and pkgnames. Before using the dependency
- checker you must build a database which reflects the properties and
- files in your system.
-
elfcmp
Compares two ELF modules (e.g. .o files, executables) section by
section. Useful for determining whether "trivial" changes -
cstyle, lint, etc - actually changed the code. The -S option
is used to test whether two binaries are the same except for
@@ -224,14 +202,10 @@
nightly build script. Takes an environment (or 'env') file describing
such things as the workspace, the parent, and what to build. See
env/developer and env/gatekeeper for sample, hopefully well-commented
env files.
-pmodes
- enforces proper file ownership and permissions in pkgmap and package
- prototype* files. converts files if necessary
-
protocmp
compares proto lists and the package definitions. Used by nightly
to determine if the proto area matches the packages, and to detect
differences between a childs proto area and a parents.
@@ -277,12 +251,11 @@
'developer' environment file to a new name (private to you and/or the
work being done in this workspace, to avoid collisions with others). Then
edit the file and tailor it to your workspace. Remember that this file
is a shell script, so it can do more than set environment variables.
-2. Login as 'gk' (or root, but your PATH and .make.machines for dmake will
- not be right). Run 'nightly' and give it your environment file as an
+2. Run 'nightly' and give it your environment file as an
option. 'nightly' will first look for your environment file in
/opt/onbld/env, and if it's not there then it will look for it as an
absolute or relative path. Some people put their environment files in
their workspace to keep them close.