src/tools/README.tools

5 # Common Development and Distribution License (the "License").
11 # and limitations under the License.
14 # file and include the License file at usr/src/OPENSOLARIS.LICENSE.
22 # Copyright (c) 1999, 2010, Oracle and/or its affiliates. All rights reserved.
27 machines. From here, 'make install' will build and install the tools
30 /opt/onbld directory, and create a root account for building called 'gk',
31 which uses csh and has a home directory of /opt/onbld/gk. You can
34 file for dmake, and has a .login that sets up for dmake.
40 	contains Solaris ABI database (ABI_*.db) and exceptions
67         tools expecting only one supported version of python, and for
80 	used with 'nightly,' and starts a shell with the environment
84 	sets the environment up differently and may cause everything
89 	of uts, and in usr/src. Uses cscope-fast.
100 	build results.  It also uses the -i option to obtain NEEDED and RUNPATH
101 	entries, which help detect changes in software dependencies and makes
105 	Runs protocmp and protolist on a workspace (or uses the environment
118 	that finds crypto modules in $ROOT and signs them using
119 	signit; and codesign_server.pl, the code that runs on the
140 	Decode and display CTF data stored in a raw file or in an ELF file.
147 	is not a definitive dependency check, but it does use "strings" and
149 	tool can handle filenames and pkgnames.  Before using the dependency
150 	checker you must build a database which reflects the properties and
163 	process and format is the same as will be used on the target
168 	It uses elfsign to sign a copy of the object and elfcmp -S to
173 	Search a directory tree for ELF objects, and produce one line of
174 	output per object. Used by check_rtime and interface_check to locate
179 	certain time and are not in a specified list of exceptions.  Since
180 	'nightly' timestamps the start of the build, and findunref uses its
184 	workspaces from both architectures and the results need to be merged.
185 	For instance, if $INTELSRC and $SPARCSRC are set to the usr/src
186 	directories of your Intel and SPARC nightly workspaces, then you
210 	well-known, never-changing password entries like 'root' and 'sys.'
213 	detects and reports invalid versioning in ELF objects.
219 	interface_check, and flags invalid deviations in ELF object
233 	RPC/MSRPC and SMB/CIFS.  ndrgen takes an input protocol definition
234 	file (say, proto.ndl) and generates an output C source file
240 	such things as the workspace, the parent, and what to build. See
241 	env/developer and env/gatekeeper for sample, hopefully well-commented
245 	enforces proper file ownership and permissions in pkgmap and package
249 	compares proto lists and the package definitions. Used by nightly
250 	to determine if the proto area matches the packages, and to detect
251 	differences between a childs proto area and a parents.
268 	Display the history, comments and diffs, of a file under SCCS
284 	to pull headers and libraries from the proto area of the parent if
289 	and warnings.
303 	lists of checked-out files and proposed SCCS comments.
307 	and the top-level directory of the workspace.
321    'developer' environment file to a new name (private to you and/or the
323    edit the file and tailor it to your workspace. Remember that this file
326 2. Login as 'gk' (or root, but your PATH and .make.machines for dmake will
327    not be right). Run 'nightly' and give it your environment file as an
329    /opt/onbld/env, and if it's not there then it will look for it as an
336    $CODEMGR_WS/log/log.<date>/nightly.log (the mail_msg it sent and the proto
338    'make clobber' and 'make install' output in $SRC, under names like
339    clobber-${MACH}.out and install-${MACH}.out (for a DEBUG build). These
340    will be smaller than nightly.log, and maybe more searchable.