2 .\" "
   3 .\" " The contents of this file are subject to the terms of the
   4 .\" " Common Development and Distribution License (the "License").
   5 .\" " You may not use this file except in compliance with the License.
   6 .\" "
   7 .\" " You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
   8 .\" " or http://www.opensolaris.org/os/licensing.
   9 .\" " See the License for the specific language governing permissions
  10 .\" " and limitations under the License.
  11 .\" "
  12 .\" " When distributing Covered Code, include this CDDL HEADER in each
  13 .\" " file and include the License file at usr/src/OPENSOLARIS.LICENSE.
  14 .\" " If applicable, add the following below this CDDL HEADER, with the
  15 .\" " fields enclosed by brackets "[]" replaced with your own identifying
  16 .\" " information: Portions Copyright [yyyy] [name of copyright owner]
  17 .\" "
  18 .\" " CDDL HEADER END
  19 .\" "
  20 .\" " Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved.
  21 .\" "
  22 .TH wsdiff 1 "15 Jul 2010"
  23 .I wsdiff
  24 \- report differences between proto area objects
  25 .SH SYNOPSIS
  26 \fBwsdiff [-dvVst] [-r \fIresults\fP] [-i \fIfilelist\fP] \fIold\fP \fInew\fP
  27 .LP
  28 .SH DESCRIPTION
  29 .IX "OS-Net build tools" "wsdiff" "" "\fBwsdiff\fP"
  30 .LP
  31 The wsdiff utility detects and reports on object differences found between
  32 two proto areas constructed from the same workspace. This can be useful
  33 when trying to understand which objects have changed as a result of a particular
  34 source change.
  35 .LP
  36 \fIold\fP specifies the baseline proto area constructed without the source
  37 change. \fInew\fP specifies the proto area constructed with the source
  38 change. Both \fIold\fP and \fInew\fP should be constructed from the same
  39 workspace, otherwise wsdiff will find object differences not associated
  40 with the source change.
  41 .SH OPTIONS
  42 .TP 10

 151 
 152 ...
 153 
 154 .fi
 155 .PP
 156 \fBExample 3: Using an input file list\fR
 157 .PP
 158 The -i option tells wsdiff to compare a specific list of objects. This can be useful
 159 in conjunction with other options that direct wsdiff to log more verbosely, allowing
 160 one to "drill down" into a particular object's differences:
 161 .LP
 162 .nf
 163 user@example$ echo "usr/lib/mdb/kvm/sparcv9/genunix.so" > flist
 164 user@example$ wsdiff -vV -r results -i flist proto.old proto
 165 usr/lib/mdb/kvm/sparcv9/genunix.so
 166 
 167 user@example$ cat results
 168 <... verbose differences only for genunix.so ...>
 169 .fi
 170 .PP
 171 \fBExample 4: Invoking wsdiff through nightly(1)\fR
 172 .PP
 173 By specifying -w in NIGHTLY_OPTIONS, nightly(1) will use wsdiff(1) to determine
 174 which objects look different, compared to the previous build. A pre-existing proto area
 175 must exist for wsdiff(1) to compare against. nightly(1) will move aside the
 176 pre-existing proto area (renaming it to $ROOT.prev under proto), and will
 177 invoke wsdiff at the end of the build. The list of changed objects will be reported
 178 in the nightly mail message, and a results file "wsdiff_results" will appear in the
 179 nightly log area.
 180 .PP
 181 \fBExample 5: Influencing the level of paralelism\fR
 182 .PP
 183 wsdiff spawns a number of threads by default after it determines the list
 184 of files for comparison. Default number of threads is based on the number of
 185 on-line CPUs present in the system. To set the number of threads for processing
 186 to some other value the DMAKE_MAX_JOBS environment variable can be used:
 187 .LP
 188 .nf
 189 $ DMAKE_MAX_JOBS=24 wsdiff proto_base proto_patch
 190 .fi
 191 .PP
 192 Note that this variable is also used for nightly(1) so when run from
 193 nightly(1), wsdiff will honor the setting.
 194 .LP
 195 .SH SEE ALSO
 196 .LP
 197 .IR lintdump(1),
 198 .IR nightly(1),
 199 .IR elfdump(1),

   2 .\" "
   3 .\" " The contents of this file are subject to the terms of the
   4 .\" " Common Development and Distribution License (the "License").
   5 .\" " You may not use this file except in compliance with the License.
   6 .\" "
   7 .\" " You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
   8 .\" " or http://www.opensolaris.org/os/licensing.
   9 .\" " See the License for the specific language governing permissions
  10 .\" " and limitations under the License.
  11 .\" "
  12 .\" " When distributing Covered Code, include this CDDL HEADER in each
  13 .\" " file and include the License file at usr/src/OPENSOLARIS.LICENSE.
  14 .\" " If applicable, add the following below this CDDL HEADER, with the
  15 .\" " fields enclosed by brackets "[]" replaced with your own identifying
  16 .\" " information: Portions Copyright [yyyy] [name of copyright owner]
  17 .\" "
  18 .\" " CDDL HEADER END
  19 .\" "
  20 .\" " Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved.
  21 .\" "
  22 .TH wsdiff 1ONBLD "15 Jul 2010"
  23 .I wsdiff
  24 \- report differences between proto area objects
  25 .SH SYNOPSIS
  26 \fBwsdiff [-dvVst] [-r \fIresults\fP] [-i \fIfilelist\fP] \fIold\fP \fInew\fP
  27 .LP
  28 .SH DESCRIPTION
  29 .IX "OS-Net build tools" "wsdiff" "" "\fBwsdiff\fP"
  30 .LP
  31 The wsdiff utility detects and reports on object differences found between
  32 two proto areas constructed from the same workspace. This can be useful
  33 when trying to understand which objects have changed as a result of a particular
  34 source change.
  35 .LP
  36 \fIold\fP specifies the baseline proto area constructed without the source
  37 change. \fInew\fP specifies the proto area constructed with the source
  38 change. Both \fIold\fP and \fInew\fP should be constructed from the same
  39 workspace, otherwise wsdiff will find object differences not associated
  40 with the source change.
  41 .SH OPTIONS
  42 .TP 10

 151 
 152 ...
 153 
 154 .fi
 155 .PP
 156 \fBExample 3: Using an input file list\fR
 157 .PP
 158 The -i option tells wsdiff to compare a specific list of objects. This can be useful
 159 in conjunction with other options that direct wsdiff to log more verbosely, allowing
 160 one to "drill down" into a particular object's differences:
 161 .LP
 162 .nf
 163 user@example$ echo "usr/lib/mdb/kvm/sparcv9/genunix.so" > flist
 164 user@example$ wsdiff -vV -r results -i flist proto.old proto
 165 usr/lib/mdb/kvm/sparcv9/genunix.so
 166 
 167 user@example$ cat results
 168 <... verbose differences only for genunix.so ...>
 169 .fi
 170 .PP
 171 \fBExample 4: Invoking wsdiff through nightly(1ONBLD)\fR
 172 .PP
 173 By specifying -w in NIGHTLY_OPTIONS, nightly(1ONBLD) will use wsdiff(1ONBLD) to determine
 174 which objects look different, compared to the previous build. A pre-existing proto area
 175 must exist for wsdiff(1ONBLD) to compare against. nightly(1ONBLD) will move aside the
 176 pre-existing proto area (renaming it to $ROOT.prev under proto), and will
 177 invoke wsdiff at the end of the build. The list of changed objects will be reported
 178 in the nightly mail message, and a results file "wsdiff_results" will appear in the
 179 nightly log area.
 180 .PP
 181 \fBExample 5: Influencing the level of paralelism\fR
 182 .PP
 183 wsdiff spawns a number of threads by default after it determines the list
 184 of files for comparison. Default number of threads is based on the number of
 185 on-line CPUs present in the system. To set the number of threads for processing
 186 to some other value the DMAKE_MAX_JOBS environment variable can be used:
 187 .LP
 188 .nf
 189 $ DMAKE_MAX_JOBS=24 wsdiff proto_base proto_patch
 190 .fi
 191 .PP
 192 Note that this variable is also used for nightly(1ONBLD) so when run from
 193 nightly(1ONBLD), wsdiff will honor the setting.
 194 .LP
 195 .SH SEE ALSO
 196 .LP
 197 .IR nightly(1ONBLD),

 198 .IR elfdump(1),