Print this page
4526 nightly contains a great deal of effectively dead code
| Split |
Close |
| Expand all |
| Collapse all |
--- old/usr/src/tools/scripts/nightly.1
+++ new/usr/src/tools/scripts/nightly.1
1 1 .\" "
2 2 .\" " The contents of this file are subject to the terms of the
3 3 .\" " Common Development and Distribution License (the "License").
4 4 .\" " You may not use this file except in compliance with the License.
5 5 .\" "
6 6 .\" " You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
7 7 .\" " or http://www.opensolaris.org/os/licensing.
8 8 .\" " See the License for the specific language governing permissions
9 9 .\" " and limitations under the License.
10 10 .\" "
11 11 .\" " When distributing Covered Code, include this CDDL HEADER in each
12 12 .\" " file and include the License file at usr/src/OPENSOLARIS.LICENSE.
13 13 .\" " If applicable, add the following below this CDDL HEADER, with the
14 14 .\" " fields enclosed by brackets "[]" replaced with your own identifying
15 15 .\" " information: Portions Copyright [yyyy] [name of copyright owner]
16 16 .\" "
17 17 .\" " CDDL HEADER END
18 18 .\" "
19 19 .\" "Copyright (c) 1999, 2010, Oracle and/or its affiliates. All rights reserved.
20 20 .\" "Copyright 2012 Joshua M. Clulow <josh@sysmgr.org>
21 21 .\" "
22 22 .TH nightly 1 "6 July 2010"
23 23 .SH NAME
24 24 .I nightly
25 25 \- build an OS-Net consolidation overnight
26 26 .SH SYNOPSIS
27 27 \fBnightly [-in] [-V VERS] <env_file>\fP
28 28 .LP
29 29 .SH DESCRIPTION
30 30 .IX "OS-Net build tools" "nightly" "" "\fBnightly\fP"
31 31 .LP
32 32 .I nightly,
33 33 the mother of all build scripts,
34 34 can bringover, build, archive, package, error check, and
35 35 generally do everything it takes to
36 36 turn OS/Net consolidation source code into useful stuff.
37 37 It is customizable to permit you to run anything from a
38 38 simple build to all of the cross-checking a gatekeeper
39 39 needs. The advantage to using
40 40 .I nightly
41 41 is that you build things correctly, consistently and
42 42 automatically, with the best practices; building with
43 43 .I nightly
44 44 can mean never having to say you're sorry to your
45 45 gatekeeper.
46 46 .LP
47 47 More
48 48 specifically,
49 49 .I nightly
50 50 performs the following tasks, in order, if
51 51 all these things are desired:
52 52 .LP
53 53 .RS
54 54 .TP
55 55 \(bu
56 56 perform a "make clobber" to clean up old binaries
57 57 .TP
58 58 \(bu
59 59 bringover from the identified parent gate/clone
60 60 .TP
61 61 \(bu
62 62 perform non-DEBUG and DEBUG builds
63 63 .TP
64 64 \(bu
65 65 list proto area files and compare with previous list
66 66 .TP
67 67 \(bu
68 68 copy updated proto area to parent
69 69 .TP
70 70 \(bu
71 71 list shared lib interface and compare with previous list
72 72 .TP
73 73 \(bu
74 74 perform a "make lint" of the kernel and report errors
75 75 .TP
76 76 \(bu
77 77 perform a "make check" to report hdrchk/cstyle errors
78 78 .TP
79 79 \(bu
80 80 report the presence of any core files
81 81 .TP
82 82 \(bu
83 83 check the ELF runtime attributes of all dynamic objects
84 84 .TP
85 85 \(bu
86 86 check for unreferenced files
87 87 .TP
88 88 \(bu
89 89 report on which proto area objects have changed (since the last build)
90 90 .TP
91 91 \(bu
92 92 report the total build time
93 93 .TP
94 94 \(bu
95 95 save a detailed log file for reference
96 96 .TP
97 97 \(bu
98 98 mail the user a summary of the completed build
99 99 .RE
100 100 .LP
101 101 The actions of the script are almost completely determined by
102 102 the environment variables in the
103 103 .I env
104 104 file, the only necessary argument. Ths only thing you really
105 105 need to use
106 106 .I nightly
107 107 is an
108 108 .I env
109 109 file that does what you want.
110 110 .LP
111 111 Like most of the other build tools in usr/src/tools, this script tends
112 112 to change on a fairly regular basis; do not expect to be able to build
113 113 OS/Net with a version of nightly significantly older than your source
114 114 tree. It has what is effectively a Consolidation Private relationship
115 115 to other build tools and with many parts of the OS/Net makefiles,
116 116 although it may also be used to build other consolidations.
117 117 .LP
118 118 .SH NIGHTLY_OPTIONS
119 119 The environment variable NIGHTLY_OPTIONS controls the actions
120 120 .I nightly
121 121 will take as it proceeds.
122 122 The -i, -n, +t and -V options may also be used from the command
123 123 line to control the actions without editing your environment file.
124 124 The -i and -n options complete the build more quickly by bypassing
125 125 some actions. If NIGHTLY_OPTIONS is not set, then "-Bmt" build
126 126 options will be used.
127 127
128 128 .B Basic action options
129 129 .TP 10
130 130 .B \-D
131 131 Do a build with DEBUG on (non-DEBUG is built by default)
132 132 .TP
133 133 .B \-F
134 134 Do _not_ do a non-DEBUG build (use with -D to get just a DEBUG build)
135 135 .TP
136 136 .B \-M
137 137 Do not run pmodes (safe file permission checker)
138 138 .TP
|
↓ open down ↓ |
138 lines elided |
↑ open up ↑ |
139 139 .B \-i
140 140 Do an incremental build, suppressing the "make clobber" that by
141 141 default removes all existing binaries and derived files. From the
142 142 command line, -i also suppresses the lint pass and the cstyle/hdrchk
143 143 pass
144 144 .TP
145 145 .B \-n
146 146 Suppress the bringover so that the build will start immediately with
147 147 current source code
148 148 .TP
149 -.B \-o
150 -Do an "old style" (pre-S10) build using root privileges to set OWNER
151 -and GROUP from the Makefiles.
152 -.TP
153 149 .B \-p
154 150 Create packages for regular install
155 151 .TP
156 152 .B \-U
157 153 Update proto area in the parent workspace
158 154 .TP
159 155 .B \-u
160 156 Update the parent workspace with files generated by the build, as follows.
161 157 .RS
162 158 .TP
163 159 \(bu
164 160 Copy proto_list_${MACH} and friends to usr/src in the parent.
165 161 .TP
166 162 \(bu
167 163 When used with -f, build a usr/src/unrefmaster.out in
168 164 the parent by merging all the usr/src/unref-${MACH}.out files in the
169 165 parent.
170 166 .TP
171 167 \(bu
172 168 When used with -A or -r, copy the contents of the resulting
173 169 ELF-data.${MACH} directory to usr/src/ELF-data.${MACH} in the parent
174 170 workspace.
175 171 .RE
176 172 .TP
177 173 .B \-m
178 174 Send mail to $MAILTO at end of build
179 175 .TP
180 176 .B \-t
181 177 Build and use the tools in $SRC/tools (default setting).
182 178 .TP
183 179 .B \+t
184 180 Use the build tools in "$ONBLD_TOOLS/bin".
185 181
186 182 .LP
187 183 .B Code checking options
188 184 .TP 10
189 185 .B \-A
190 186 Check for ABI discrepancies in .so files.
191 187 It is only required for shared object developers when there is an
192 188 addition, deletion or change of interface in the .so files.
193 189 .TP
194 190 .B \-C
195 191 Check for cstyle/hdrchk errors
196 192 .TP
197 193 .B \-f
198 194 Check for unreferenced files. Since the full workspace must be built
199 195 in order to accurately identify unreferenced files, -f is ignored for
200 196 incremental (-i) builds, or builds that do not include -l, and -p.
201 197 .TP
|
↓ open down ↓ |
39 lines elided |
↑ open up ↑ |
202 198 .B \-r
203 199 Check the ELF runtime attributes of all dynamic objects
204 200 .TP
205 201 .B \-l
206 202 Do "make lint" in $LINTDIRS (default: $SRC n)
207 203 .TP
208 204 .B \-N
209 205 Do not run protocmp or checkpaths (note: this option is not
210 206 recommended, especially in conjunction with the \-p option)
211 207 .TP
212 -.B \-W
213 -Do not report warnings (for freeware gate ONLY)
214 -.TP
215 208 .B \-w
216 209 Report which proto area objects differ between this and the last build.
217 210 See wsdiff(1) for details. Note that the proto areas used for comparison
218 211 are the last ones constructed as part of the build. As an example, if both
219 212 a non-debug and debug build are performed (in that order), then the debug
220 213 proto area will be used for comparison (which might not be what you want).
221 214 .LP
222 215 .B Groups of options
223 216 .TP 10
224 217 .B \-G
225 218 Gate keeper default group of options (-u)
226 219 .TP
227 220 .B \-I
|
↓ open down ↓ |
3 lines elided |
↑ open up ↑ |
228 221 Integration engineer default group of options (-mpu)
229 222 .TP
230 223 .B \-R
231 224 Default group of options for building a release (-mp)
232 225
233 226 .LP
234 227 .B Miscellaneous options
235 228 .TP 10
236 229 .B \-V VERS
237 230 set the build version string to VERS, overriding VERSION
238 -.TP
239 -.B \-X
240 -Copies the proto area and packages from the IHV and IHV-bin gates into the
241 -nightly proto and package areas. This is only available on i386. See
242 -.B REALMODE ENVIRONMENT VARIABLES
243 -and
244 -.B BUILDING THE IHV WORKSPACE
245 -below.
246 231
247 232 .LP
248 233 .SH ENVIRONMENT VARIABLES
249 234 .LP
250 235 Here is a list of prominent environment variables that
251 236 .I nightly
252 237 references and the meaning of each variable.
253 238 .LP
254 239 .RE
255 240 .B CODEMGR_WS
256 241 .RS 5
257 242 The root of your workspace, including whatever metadata is kept by
258 243 the source code management system. This is the workspace in which the
259 244 build will be done.
260 245 .RE
261 246 .LP
262 247 .B PARENT_WS
263 248 .RS 5
264 249 The root of the workspace that is the parent of the
265 250 one being built. This is particularly relevant for configurations
266 251 with a main
267 252 workspace and build workspaces underneath it; see the
268 253 \-u and \-U
269 254 options as well as the PKGARCHIVE environment variable, for more
270 255 information.
|
↓ open down ↓ |
15 lines elided |
↑ open up ↑ |
271 256 .RE
272 257 .LP
273 258 .B BRINGOVER_WS
274 259 .RS 5
275 260 This is the workspace from which
276 261 .I nightly
277 262 will fetch sources to either populate or update your workspace;
278 263 it defaults to $CLONE_WS.
279 264 .RE
280 265 .LP
281 -.B CLOSED_BRINGOVER_WS
282 -.RS 5
283 -A full Mercurial workspace has two repositories: one for open source
284 -and one for closed source. If this variable is non-null,
285 -.I nightly
286 -will pull from the repository that it names to get the closed source.
287 -It defaults to $CLOSED_CLONE_WS.
288 -.LP
289 -If $CODEMGR_WS already exists and contains only the open repository,
290 -.I nightly
291 -will ignore this variable; you'll need to pull the closed repository
292 -by hand if you want it.
293 -.RE
294 -.LP
295 266 .B CLONE_WS
296 267 .RS 5
297 268 This is the workspace from which
298 269 .I nightly
299 270 will fetch sources by default. This is
300 271 often distinct from the parent, particularly if the parent is a gate.
301 272 .RE
302 273 .LP
303 -.B CLOSED_CLONE_WS
304 -.RS 5
305 -This is the default closed-source Mercurial repository that
306 -.I nightly
307 -might pull from (see
308 -.B CLOSED_BRINGOVER_WS
309 -for details).
310 -.RE
311 -.LP
312 274 .B SRC
313 275 .RS 5
314 276 Root of OS-Net source code, referenced by the Makefiles. It is
315 277 the starting point of build activity. It should be expressed
316 278 in terms of $CODEMGR_WS.
317 279 .RE
318 280 .LP
319 281 .B ROOT
320 282 .RS 5
321 283 Root of the proto area for the build. The makefiles direct
322 284 installation of build products to this area and
323 285 direct references to these files by builds of commands and other
324 286 targets. It should be expressed in terms of $CODEMGR_WS.
325 287 .LP
326 288 If $MULTI_PROTO is "no", $ROOT may contain a DEBUG or non-DEBUG
327 289 build. If $MULTI_PROTO is "yes", $ROOT contains the DEBUG build and
328 290 $ROOT-nd contains the non-DEBUG build.
329 291 .RE
330 292 .LP
331 293 .B TOOLS_ROOT
332 294 .RS 5
333 295 Root of the tools proto area for the build. The makefiles direct
334 296 installation of tools build products to this area. Unless \fB+t\fR
335 297 is part of $NIGHTLY_OPTIONS, these tools will be used during the
336 298 build.
337 299 .LP
338 300 As built by nightly, this will always contain non-DEBUG objects.
339 301 Therefore, this will always have a -nd suffix, regardless of
340 302 $MULTI_PROTO.
341 303 .RE
342 304 .LP
343 305 .B MACH
344 306 .RS 5
345 307 The instruction set architecture of the build machine as given
346 308 by \fIuname -p\fP, e.g. sparc, i386.
347 309 .RE
348 310 .LP
349 311 .B LOCKNAME
350 312 .RS 5
351 313 The name of the file used to lock out multiple runs of
352 314 .IR nightly .
353 315 This should generally be left to the default setting.
354 316 .RE
355 317 .LP
356 318 .B ATLOG
357 319 .RS 5
358 320 The location of the log directory maintained by
359 321 .IR nightly .
360 322 This should generally be left to the default setting.
361 323 .RE
362 324 .LP
363 325 .B LOGFILE
364 326 .RS 5
365 327 The name of the log file in the $ATLOG directory maintained by
366 328 .IR nightly .
367 329 This should generally be left to the default setting.
368 330 .RE
369 331 .LP
370 332 .B STAFFER
371 333 .RS 5
372 334 The non-root account to use on the build machine for the
373 335 bringover from the clone or parent workspace.
374 336 This may not be the same identify used by the SCM.
375 337 .RE
376 338 .LP
377 339 .B MAILTO
378 340 .RS 5
379 341 The address to be used to send completion e-mail at the end of
380 342 the build (for the \-m option).
381 343 .RE
382 344 .LP
383 345 .B MAILFROM
384 346 .RS 5
385 347 The address to be used for From: in the completion e-mail at the
386 348 end of the build (for the \-m option).
387 349 .RE
388 350 .LP
389 351 .B REF_PROTO_LIST
390 352 .RS 5
391 353 Name of file used with protocmp to compare proto area contents.
392 354 .RE
393 355 .LP
394 356 .B PARENT_ROOT
395 357 .RS 5
396 358 The parent root, which is the destination for copying the proto
397 359 area(s) when using the \-U option.
398 360 .RE
399 361 .LP
400 362 .B PARENT_TOOLS_ROOT
401 363 .RS 5
402 364 The parent tools root, which is the destination for copying the tools
403 365 proto area when using the \-U option.
404 366 .RE
405 367 .LP
406 368 .B RELEASE
407 369 .RS 5
408 370 The release version number to be used; e.g., 5.10.1 (Note: this is set
409 371 in Makefile.master and should not normally be overridden).
410 372 .RE
411 373 .LP
412 374 .B VERSION
413 375 .RS 5
414 376 The version text string to be used; e.g., "onnv:`date '+%Y-%m-%d'`".
415 377 .RE
416 378 .LP
417 379 .B RELEASE_DATE
418 380 .RS 5
419 381 The release date text to be used; e.g., October 2009. If not set in
420 382 your environment file, then this text defaults to the output from
421 383 $(LC_ALL=C date +"%B %Y"); e.g., "October 2009".
422 384 .RE
423 385 .LP
424 386 .B RELEASE_BUILD
425 387 .RS 5
426 388 Define this to build a release with a non-DEBUG kernel.
427 389 Generally, let
428 390 .I nightly
429 391 set this for you based on its options.
430 392 .RE
431 393 .LP
432 394 .B PKGARCHIVE
433 395 .RS 5
434 396 The destination for packages. This may be relative to
435 397 $CODEMGR_WS for private packages or relative to $PARENT_WS
436 398 if you have different workspaces for different architectures
437 399 but want one hierarchy of packages.
438 400 .RE
439 401 .LP
440 402 .B MAKEFLAGS
441 403 .RS 5
442 404 Set default flags to make; e.g., -k to build all targets regardless of errors.
443 405 .RE
444 406 .LP
445 407 .B UT_NO_USAGE_TRACKING
446 408 .RS 5
447 409 Disables usage reporting by listed Devpro tools. Otherwise it sends mail
448 410 to some Devpro machine every time the tools are used.
449 411 .RE
450 412 .LP
451 413 .B LINTDIRS
452 414 .RS 5
453 415 Directories to lint with the \-l option.
454 416 .RE
455 417 .LP
456 418 .B BUILD_TOOLS
457 419 .RS 5
458 420 BUILD_TOOLS is the root of all tools including the compilers; e.g.,
459 421 /ws/onnv-tools. It is used by the makefile system, but not nightly.
460 422 .RE
461 423 .LP
462 424 .B ONBLD_TOOLS
463 425 .RS 5
464 426 ONBLD_TOOLS is the root of all the tools that are part of SUNWonbld; e.g.,
465 427 /ws/onnv-tools/onbld. By default, it is derived from
466 428 .BR BUILD_TOOLS .
467 429 It is used by the makefile system, but not nightly.
468 430 .RE
469 431 .LP
470 432 .B SPRO_ROOT
471 433 .RS 5
472 434 The gate-defined default location for the Sun compilers, e.g.
473 435 /ws/onnv-tools/SUNWspro. By default, it is derived from
474 436 .BR BUILD_TOOLS .
475 437 It is used by the makefile system, but not nightly.
476 438 .RE
477 439 .LP
478 440 .B JAVA_ROOT
479 441 .RS 5
480 442 The location for the java compilers for the build, generally /usr/java.
481 443 .RE
482 444 .LP
483 445 .B OPTHOME
484 446 .RS 5
485 447 The gate-defined default location of things formerly in /opt; e.g.,
486 448 /ws/onnv-tools. This is used by nightly, but not the makefiles.
487 449 .RE
488 450 .LP
489 451 .B TEAMWARE
490 452 .RS 5
491 453 The gate-defined default location for the Teamware tools; e.g.,
492 454 /ws/onnv-tools/SUNWspro. By default, it is derived from
493 455 .BR OPTHOME .
494 456 This is used by nightly, but not the makefiles. There is no
495 457 corresponding variable for Mercurial or Subversion, which are assumed
496 458 to be installed in the default path.
|
↓ open down ↓ |
175 lines elided |
↑ open up ↑ |
497 459 .RE
498 460 .LP
499 461 .B ON_CLOSED_BINS
500 462 .RS 5
501 463 OpenSolaris builds do not contain the closed source tree. Instead,
502 464 the developer downloads a closed binaries tree and unpacks it.
503 465 .B ON_CLOSED_BINS
504 466 tells nightly
505 467 where to find these closed binaries, so that it can add them into the
506 468 build.
507 -.LP
508 469 .RE
509 -.B ON_CRYPTO_BINS
510 -.RS 5
511 -This is the path to a compressed tarball that contains debug
512 -cryptographic binaries that have been signed to allow execution
513 -outside of Sun, e.g., $PARENT_WS/packages/$MACH/on-crypto.$MACH.bz2.
514 -.I nightly
515 -will automatically adjust the path for non-debug builds. This tarball
516 -is needed if the closed-source tree is not present. Also, it is
517 -usually needed when generating OpenSolaris deliverables from a project
518 -workspace. This is because most projects do not have access to the
519 -necessary key and certificate that would let them sign their own
520 -cryptographic binaries.
521 470 .LP
522 -.RE
523 471 .B CHECK_PATHS
524 472 .RS 5
525 473 Normally, nightly runs the 'checkpaths' script to check for
526 474 discrepancies among the files that list paths to other files, such as
527 475 exception lists and req.flg. Set this flag to 'n' to disable this
528 476 check, which appears in the nightly output as "Check lists of files."
529 477 .RE
530 478 .LP
531 479 .B CHECK_DMAKE
532 480 .RS 5
533 481 Nightly validates that the version of dmake encountered is known to be
534 482 safe to use. Set this flag to 'n' to disable this test, allowing any
535 483 version of dmake to be used.
536 484 .RE
537 485 .LP
538 486 .B MULTI_PROTO
539 487 .RS 5
540 488 If "no" (the default),
541 489 .I nightly
542 490 will reuse $ROOT for both the DEBUG and non-DEBUG builds. If "yes",
543 491 the DEBUG build will go in $ROOT and the non-DEBUG build will go in
544 492 $ROOT-nd. Other values will be treated as "no".
545 493 .RE
546 494 .LP
547 495 .SH NIGHTLY HOOK ENVIRONMENT VARIABLES
548 496 .LP
549 497 Several optional environment variables may specify commands to run at
550 498 various points during the build. Commands specified in the hook
551 499 variable will be run in a subshell; command output will be appended to
552 500 the mail message and log file. If the hook exits with a non-zero
553 501 status, the build is aborted immediately. Environment variables
554 502 defined in the environment file will be available.
555 503 .LP
556 504 .B SYS_PRE_NIGHTLY
557 505 .RS 5
558 506 Run just after the workspace lock is acquired. This is reserved for
559 507 per-build-machine customizations and should be set only in /etc/nightly.conf
560 508 .RE
561 509 .LP
562 510 .B PRE_NIGHTLY
563 511 .RS 5
564 512 Run just after SYS_PRE_NIGHTLY.
565 513 .RE
566 514 .LP
567 515 .B PRE_BRINGOVER
568 516 .RS 5
569 517 Run just before bringover is started; not run if no bringover is done.
570 518 .RE
571 519 .LP
572 520 .B POST_BRINGOVER
573 521 .RS 5
574 522 Run just after bringover completes; not run if no bringover is done.
575 523 .RE
576 524 .LP
577 525 .B POST_NIGHTLY
578 526 .RS 5
579 527 Run after the build completes, with the return status of nightly - one
|
↓ open down ↓ |
47 lines elided |
↑ open up ↑ |
580 528 of "Completed", "Interrupted", or "Failed" - available in the
581 529 environment variable NIGHTLY_STATUS.
582 530 .RE
583 531 .LP
584 532 .B SYS_POST_NIGHTLY
585 533 .RS 5
586 534 This is reserved for per-build-machine customizations, and runs
587 535 immedately after POST_NIGHTLY.
588 536 .RE
589 537 .LP
590 -.SH REALMODE ENVIRONMENT VARIABLES
591 -.LP
592 -The following environment variables referenced by
593 -.I nightly
594 -are only required when the -X option is used.
595 -.LP
596 -.RE
597 -.B IA32_IHV_WS
598 -.RS 5
599 -Reference to the IHV workspace containing IHV driver binaries.
600 -The IHV workspace must be fully built before starting the ON realmode build.
601 -.LP
602 -.RE
603 -.B IA32_IHV_ROOT
604 -.RS 5
605 -Reference to the IHV workspace proto area.
606 -The IHV workspace must be fully built before starting the ON realmode build.
607 -.LP
608 -.RE
609 -.B IA32_IHV_PKGS
610 -.RS 5
611 -Reference to the IHV workspace packages. If this is empty or the directory
612 -is non-existent, then nightly will skip copying the packages.
613 -.LP
614 -.RE
615 -.B IA32_IHV_BINARY_PKGS
616 -.RS 5
617 -Reference to binary-only IHV packages. If this is empty or the directory
618 -is non-existent, then nightly will skip copying the packages.
619 -.LP
620 -.RE
621 -.B SPARC_RM_PKGARCHIVE
622 -.RS 5
623 -Destination for sparc realmode package SUNWrmodu.
624 -Yes, this sparc package really is built on x86.
625 538 .SH FILES
626 539 .LP
627 540 .RS 5
628 541 /etc/nightly.conf
629 542 .RE
630 543 .LP
631 544 If present, nightly executes this file just prior to executing the
632 545 .I env
633 546 file.
634 -.SH BUILDING THE IHV WORKSPACE
635 -.LP
636 -The IHV workspace can be built with
637 -.I nightly.
638 -The recommended options are:
639 -.LP
640 -.RS 5
641 -NIGHTLY_OPTIONS="-pmWN"
642 -.RE
643 -.LP
644 -None of the realmode environment variables needed for ON realmode builds
645 -are required to build the IHV workspace.
646 547 .SH EXAMPLES
647 548 .LP
648 549 Start with the example file in usr/src/tools/env/developer.sh
649 550 (or gatekeeper.sh), copy to myenv and make your changes.
650 551 .LP
651 552 .PD 0
652 553 # grep NIGHTLY_OPTIONS myenv
653 554 .LP
654 555 NIGHTLY_OPTIONS="-ACrlapDm"
655 556 .LP
656 557 export NIGHTLY_OPTIONS
657 558 .LP
658 559 # /opt/onbld/bin/nightly -i myenv
659 560 .PD
660 561 .LP
661 562 .SH SEE ALSO
662 563 .BR bldenv (1)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX