Print this page
4265 remove INTERNAL_RELEASE_BUILD
| 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
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 149 .B \-o
150 150 Do an "old style" (pre-S10) build using root privileges to set OWNER
151 151 and GROUP from the Makefiles.
152 152 .TP
153 153 .B \-p
154 154 Create packages for regular install
155 155 .TP
156 156 .B \-U
157 157 Update proto area in the parent workspace
158 158 .TP
159 159 .B \-u
160 160 Update the parent workspace with files generated by the build, as follows.
161 161 .RS
162 162 .TP
163 163 \(bu
164 164 Copy proto_list_${MACH} and friends to usr/src in the parent.
165 165 .TP
166 166 \(bu
167 167 When used with -f, build a usr/src/unrefmaster.out in
168 168 the parent by merging all the usr/src/unref-${MACH}.out files in the
169 169 parent.
170 170 .TP
171 171 \(bu
172 172 When used with -A or -r, copy the contents of the resulting
173 173 ELF-data.${MACH} directory to usr/src/ELF-data.${MACH} in the parent
174 174 workspace.
175 175 .RE
176 176 .TP
177 177 .B \-m
178 178 Send mail to $MAILTO at end of build
179 179 .TP
180 180 .B \-t
181 181 Build and use the tools in $SRC/tools (default setting).
182 182 .TP
183 183 .B \+t
184 184 Use the build tools in "$ONBLD_TOOLS/bin".
185 185
186 186 .LP
187 187 .B Code checking options
188 188 .TP 10
189 189 .B \-A
190 190 Check for ABI discrepancies in .so files.
191 191 It is only required for shared object developers when there is an
192 192 addition, deletion or change of interface in the .so files.
193 193 .TP
194 194 .B \-C
195 195 Check for cstyle/hdrchk errors
196 196 .TP
197 197 .B \-f
198 198 Check for unreferenced files. Since the full workspace must be built
199 199 in order to accurately identify unreferenced files, -f is ignored for
200 200 incremental (-i) builds, or builds that do not include -l, and -p.
201 201 .TP
202 202 .B \-r
203 203 Check the ELF runtime attributes of all dynamic objects
204 204 .TP
205 205 .B \-l
206 206 Do "make lint" in $LINTDIRS (default: $SRC n)
207 207 .TP
208 208 .B \-N
209 209 Do not run protocmp or checkpaths (note: this option is not
210 210 recommended, especially in conjunction with the \-p option)
211 211 .TP
212 212 .B \-W
213 213 Do not report warnings (for freeware gate ONLY)
214 214 .TP
215 215 .B \-w
216 216 Report which proto area objects differ between this and the last build.
217 217 See wsdiff(1) for details. Note that the proto areas used for comparison
218 218 are the last ones constructed as part of the build. As an example, if both
219 219 a non-debug and debug build are performed (in that order), then the debug
220 220 proto area will be used for comparison (which might not be what you want).
221 221 .LP
222 222 .B Groups of options
223 223 .TP 10
224 224 .B \-G
225 225 Gate keeper default group of options (-u)
226 226 .TP
227 227 .B \-I
228 228 Integration engineer default group of options (-mpu)
229 229 .TP
230 230 .B \-R
231 231 Default group of options for building a release (-mp)
232 232
233 233 .LP
234 234 .B Miscellaneous options
235 235 .TP 10
236 236 .B \-V VERS
237 237 set the build version string to VERS, overriding VERSION
238 238 .TP
239 239 .B \-X
240 240 Copies the proto area and packages from the IHV and IHV-bin gates into the
241 241 nightly proto and package areas. This is only available on i386. See
242 242 .B REALMODE ENVIRONMENT VARIABLES
243 243 and
244 244 .B BUILDING THE IHV WORKSPACE
245 245 below.
246 246
247 247 .LP
248 248 .SH ENVIRONMENT VARIABLES
249 249 .LP
250 250 Here is a list of prominent environment variables that
251 251 .I nightly
252 252 references and the meaning of each variable.
253 253 .LP
254 254 .RE
255 255 .B CODEMGR_WS
256 256 .RS 5
257 257 The root of your workspace, including whatever metadata is kept by
258 258 the source code management system. This is the workspace in which the
259 259 build will be done.
260 260 .RE
261 261 .LP
262 262 .B PARENT_WS
263 263 .RS 5
264 264 The root of the workspace that is the parent of the
265 265 one being built. This is particularly relevant for configurations
266 266 with a main
267 267 workspace and build workspaces underneath it; see the
268 268 \-u and \-U
269 269 options as well as the PKGARCHIVE environment variable, for more
270 270 information.
271 271 .RE
272 272 .LP
273 273 .B BRINGOVER_WS
274 274 .RS 5
275 275 This is the workspace from which
276 276 .I nightly
277 277 will fetch sources to either populate or update your workspace;
278 278 it defaults to $CLONE_WS.
279 279 .RE
280 280 .LP
281 281 .B CLOSED_BRINGOVER_WS
282 282 .RS 5
283 283 A full Mercurial workspace has two repositories: one for open source
284 284 and one for closed source. If this variable is non-null,
285 285 .I nightly
286 286 will pull from the repository that it names to get the closed source.
287 287 It defaults to $CLOSED_CLONE_WS.
288 288 .LP
289 289 If $CODEMGR_WS already exists and contains only the open repository,
290 290 .I nightly
291 291 will ignore this variable; you'll need to pull the closed repository
292 292 by hand if you want it.
293 293 .RE
294 294 .LP
295 295 .B CLONE_WS
296 296 .RS 5
297 297 This is the workspace from which
298 298 .I nightly
299 299 will fetch sources by default. This is
300 300 often distinct from the parent, particularly if the parent is a gate.
301 301 .RE
302 302 .LP
303 303 .B CLOSED_CLONE_WS
304 304 .RS 5
305 305 This is the default closed-source Mercurial repository that
306 306 .I nightly
307 307 might pull from (see
308 308 .B CLOSED_BRINGOVER_WS
309 309 for details).
310 310 .RE
311 311 .LP
312 312 .B SRC
313 313 .RS 5
314 314 Root of OS-Net source code, referenced by the Makefiles. It is
315 315 the starting point of build activity. It should be expressed
316 316 in terms of $CODEMGR_WS.
317 317 .RE
318 318 .LP
319 319 .B ROOT
320 320 .RS 5
321 321 Root of the proto area for the build. The makefiles direct
322 322 installation of build products to this area and
323 323 direct references to these files by builds of commands and other
324 324 targets. It should be expressed in terms of $CODEMGR_WS.
325 325 .LP
326 326 If $MULTI_PROTO is "no", $ROOT may contain a DEBUG or non-DEBUG
327 327 build. If $MULTI_PROTO is "yes", $ROOT contains the DEBUG build and
328 328 $ROOT-nd contains the non-DEBUG build.
329 329 .RE
330 330 .LP
331 331 .B TOOLS_ROOT
332 332 .RS 5
333 333 Root of the tools proto area for the build. The makefiles direct
334 334 installation of tools build products to this area. Unless \fB+t\fR
335 335 is part of $NIGHTLY_OPTIONS, these tools will be used during the
336 336 build.
337 337 .LP
338 338 As built by nightly, this will always contain non-DEBUG objects.
339 339 Therefore, this will always have a -nd suffix, regardless of
340 340 $MULTI_PROTO.
341 341 .RE
342 342 .LP
343 343 .B MACH
344 344 .RS 5
345 345 The instruction set architecture of the build machine as given
346 346 by \fIuname -p\fP, e.g. sparc, i386.
347 347 .RE
348 348 .LP
349 349 .B LOCKNAME
350 350 .RS 5
351 351 The name of the file used to lock out multiple runs of
352 352 .IR nightly .
353 353 This should generally be left to the default setting.
354 354 .RE
355 355 .LP
356 356 .B ATLOG
357 357 .RS 5
358 358 The location of the log directory maintained by
359 359 .IR nightly .
360 360 This should generally be left to the default setting.
361 361 .RE
362 362 .LP
363 363 .B LOGFILE
364 364 .RS 5
365 365 The name of the log file in the $ATLOG directory maintained by
366 366 .IR nightly .
367 367 This should generally be left to the default setting.
368 368 .RE
369 369 .LP
370 370 .B STAFFER
371 371 .RS 5
372 372 The non-root account to use on the build machine for the
373 373 bringover from the clone or parent workspace.
374 374 This may not be the same identify used by the SCM.
375 375 .RE
376 376 .LP
377 377 .B MAILTO
378 378 .RS 5
379 379 The address to be used to send completion e-mail at the end of
380 380 the build (for the \-m option).
381 381 .RE
382 382 .LP
383 383 .B MAILFROM
384 384 .RS 5
385 385 The address to be used for From: in the completion e-mail at the
386 386 end of the build (for the \-m option).
387 387 .RE
388 388 .LP
389 389 .B REF_PROTO_LIST
390 390 .RS 5
391 391 Name of file used with protocmp to compare proto area contents.
392 392 .RE
393 393 .LP
394 394 .B PARENT_ROOT
395 395 .RS 5
396 396 The parent root, which is the destination for copying the proto
397 397 area(s) when using the \-U option.
398 398 .RE
399 399 .LP
400 400 .B PARENT_TOOLS_ROOT
401 401 .RS 5
402 402 The parent tools root, which is the destination for copying the tools
403 403 proto area when using the \-U option.
404 404 .RE
405 405 .LP
406 406 .B RELEASE
407 407 .RS 5
408 408 The release version number to be used; e.g., 5.10.1 (Note: this is set
409 409 in Makefile.master and should not normally be overridden).
410 410 .RE
411 411 .LP
412 412 .B VERSION
413 413 .RS 5
|
↓ open down ↓ |
413 lines elided |
↑ open up ↑ |
414 414 The version text string to be used; e.g., "onnv:`date '+%Y-%m-%d'`".
415 415 .RE
416 416 .LP
417 417 .B RELEASE_DATE
418 418 .RS 5
419 419 The release date text to be used; e.g., October 2009. If not set in
420 420 your environment file, then this text defaults to the output from
421 421 $(LC_ALL=C date +"%B %Y"); e.g., "October 2009".
422 422 .RE
423 423 .LP
424 -.B INTERNAL_RELEASE_BUILD
425 -.RS 5
426 -See Makefile.master - but it mostly controls id strings. Generally,
427 -let
428 -.I nightly
429 -set this for you.
430 -.RE
431 -.LP
432 424 .B RELEASE_BUILD
433 425 .RS 5
434 426 Define this to build a release with a non-DEBUG kernel.
435 427 Generally, let
436 428 .I nightly
437 429 set this for you based on its options.
438 430 .RE
439 431 .LP
440 432 .B PKGARCHIVE
441 433 .RS 5
442 434 The destination for packages. This may be relative to
443 435 $CODEMGR_WS for private packages or relative to $PARENT_WS
444 436 if you have different workspaces for different architectures
445 437 but want one hierarchy of packages.
446 438 .RE
447 439 .LP
448 440 .B MAKEFLAGS
449 441 .RS 5
450 442 Set default flags to make; e.g., -k to build all targets regardless of errors.
451 443 .RE
452 444 .LP
453 445 .B UT_NO_USAGE_TRACKING
454 446 .RS 5
455 447 Disables usage reporting by listed Devpro tools. Otherwise it sends mail
456 448 to some Devpro machine every time the tools are used.
457 449 .RE
458 450 .LP
459 451 .B LINTDIRS
460 452 .RS 5
461 453 Directories to lint with the \-l option.
462 454 .RE
463 455 .LP
464 456 .B BUILD_TOOLS
465 457 .RS 5
466 458 BUILD_TOOLS is the root of all tools including the compilers; e.g.,
467 459 /ws/onnv-tools. It is used by the makefile system, but not nightly.
468 460 .RE
469 461 .LP
470 462 .B ONBLD_TOOLS
471 463 .RS 5
472 464 ONBLD_TOOLS is the root of all the tools that are part of SUNWonbld; e.g.,
473 465 /ws/onnv-tools/onbld. By default, it is derived from
474 466 .BR BUILD_TOOLS .
475 467 It is used by the makefile system, but not nightly.
476 468 .RE
477 469 .LP
478 470 .B SPRO_ROOT
479 471 .RS 5
480 472 The gate-defined default location for the Sun compilers, e.g.
481 473 /ws/onnv-tools/SUNWspro. By default, it is derived from
482 474 .BR BUILD_TOOLS .
483 475 It is used by the makefile system, but not nightly.
484 476 .RE
485 477 .LP
486 478 .B JAVA_ROOT
487 479 .RS 5
488 480 The location for the java compilers for the build, generally /usr/java.
489 481 .RE
490 482 .LP
491 483 .B OPTHOME
492 484 .RS 5
493 485 The gate-defined default location of things formerly in /opt; e.g.,
494 486 /ws/onnv-tools. This is used by nightly, but not the makefiles.
495 487 .RE
496 488 .LP
497 489 .B TEAMWARE
498 490 .RS 5
499 491 The gate-defined default location for the Teamware tools; e.g.,
500 492 /ws/onnv-tools/SUNWspro. By default, it is derived from
501 493 .BR OPTHOME .
502 494 This is used by nightly, but not the makefiles. There is no
503 495 corresponding variable for Mercurial or Subversion, which are assumed
504 496 to be installed in the default path.
505 497 .RE
506 498 .LP
507 499 .B ON_CLOSED_BINS
508 500 .RS 5
509 501 OpenSolaris builds do not contain the closed source tree. Instead,
510 502 the developer downloads a closed binaries tree and unpacks it.
511 503 .B ON_CLOSED_BINS
512 504 tells nightly
513 505 where to find these closed binaries, so that it can add them into the
514 506 build.
515 507 .LP
516 508 .RE
517 509 .B ON_CRYPTO_BINS
518 510 .RS 5
519 511 This is the path to a compressed tarball that contains debug
520 512 cryptographic binaries that have been signed to allow execution
521 513 outside of Sun, e.g., $PARENT_WS/packages/$MACH/on-crypto.$MACH.bz2.
522 514 .I nightly
523 515 will automatically adjust the path for non-debug builds. This tarball
524 516 is needed if the closed-source tree is not present. Also, it is
525 517 usually needed when generating OpenSolaris deliverables from a project
526 518 workspace. This is because most projects do not have access to the
527 519 necessary key and certificate that would let them sign their own
528 520 cryptographic binaries.
529 521 .LP
530 522 .RE
531 523 .B CHECK_PATHS
532 524 .RS 5
533 525 Normally, nightly runs the 'checkpaths' script to check for
534 526 discrepancies among the files that list paths to other files, such as
535 527 exception lists and req.flg. Set this flag to 'n' to disable this
536 528 check, which appears in the nightly output as "Check lists of files."
537 529 .RE
538 530 .LP
539 531 .B CHECK_DMAKE
540 532 .RS 5
541 533 Nightly validates that the version of dmake encountered is known to be
542 534 safe to use. Set this flag to 'n' to disable this test, allowing any
543 535 version of dmake to be used.
544 536 .RE
545 537 .LP
546 538 .B MULTI_PROTO
547 539 .RS 5
548 540 If "no" (the default),
549 541 .I nightly
550 542 will reuse $ROOT for both the DEBUG and non-DEBUG builds. If "yes",
551 543 the DEBUG build will go in $ROOT and the non-DEBUG build will go in
552 544 $ROOT-nd. Other values will be treated as "no".
553 545 .RE
554 546 .LP
555 547 .SH NIGHTLY HOOK ENVIRONMENT VARIABLES
556 548 .LP
557 549 Several optional environment variables may specify commands to run at
558 550 various points during the build. Commands specified in the hook
559 551 variable will be run in a subshell; command output will be appended to
560 552 the mail message and log file. If the hook exits with a non-zero
561 553 status, the build is aborted immediately. Environment variables
562 554 defined in the environment file will be available.
563 555 .LP
564 556 .B SYS_PRE_NIGHTLY
565 557 .RS 5
566 558 Run just after the workspace lock is acquired. This is reserved for
567 559 per-build-machine customizations and should be set only in /etc/nightly.conf
568 560 .RE
569 561 .LP
570 562 .B PRE_NIGHTLY
571 563 .RS 5
572 564 Run just after SYS_PRE_NIGHTLY.
573 565 .RE
574 566 .LP
575 567 .B PRE_BRINGOVER
576 568 .RS 5
577 569 Run just before bringover is started; not run if no bringover is done.
578 570 .RE
579 571 .LP
580 572 .B POST_BRINGOVER
581 573 .RS 5
582 574 Run just after bringover completes; not run if no bringover is done.
583 575 .RE
584 576 .LP
585 577 .B POST_NIGHTLY
586 578 .RS 5
587 579 Run after the build completes, with the return status of nightly - one
588 580 of "Completed", "Interrupted", or "Failed" - available in the
589 581 environment variable NIGHTLY_STATUS.
590 582 .RE
591 583 .LP
592 584 .B SYS_POST_NIGHTLY
593 585 .RS 5
594 586 This is reserved for per-build-machine customizations, and runs
595 587 immedately after POST_NIGHTLY.
596 588 .RE
597 589 .LP
598 590 .SH REALMODE ENVIRONMENT VARIABLES
599 591 .LP
600 592 The following environment variables referenced by
601 593 .I nightly
602 594 are only required when the -X option is used.
603 595 .LP
604 596 .RE
605 597 .B IA32_IHV_WS
606 598 .RS 5
607 599 Reference to the IHV workspace containing IHV driver binaries.
608 600 The IHV workspace must be fully built before starting the ON realmode build.
609 601 .LP
610 602 .RE
611 603 .B IA32_IHV_ROOT
612 604 .RS 5
613 605 Reference to the IHV workspace proto area.
614 606 The IHV workspace must be fully built before starting the ON realmode build.
615 607 .LP
616 608 .RE
617 609 .B IA32_IHV_PKGS
618 610 .RS 5
619 611 Reference to the IHV workspace packages. If this is empty or the directory
620 612 is non-existent, then nightly will skip copying the packages.
621 613 .LP
622 614 .RE
623 615 .B IA32_IHV_BINARY_PKGS
624 616 .RS 5
625 617 Reference to binary-only IHV packages. If this is empty or the directory
626 618 is non-existent, then nightly will skip copying the packages.
627 619 .LP
628 620 .RE
629 621 .B SPARC_RM_PKGARCHIVE
630 622 .RS 5
631 623 Destination for sparc realmode package SUNWrmodu.
632 624 Yes, this sparc package really is built on x86.
633 625 .SH FILES
634 626 .LP
635 627 .RS 5
636 628 /etc/nightly.conf
637 629 .RE
638 630 .LP
639 631 If present, nightly executes this file just prior to executing the
640 632 .I env
641 633 file.
642 634 .SH BUILDING THE IHV WORKSPACE
643 635 .LP
644 636 The IHV workspace can be built with
645 637 .I nightly.
646 638 The recommended options are:
647 639 .LP
648 640 .RS 5
649 641 NIGHTLY_OPTIONS="-pmWN"
650 642 .RE
651 643 .LP
652 644 None of the realmode environment variables needed for ON realmode builds
653 645 are required to build the IHV workspace.
654 646 .SH EXAMPLES
655 647 .LP
656 648 Start with the example file in usr/src/tools/env/developer.sh
657 649 (or gatekeeper.sh), copy to myenv and make your changes.
658 650 .LP
659 651 .PD 0
660 652 # grep NIGHTLY_OPTIONS myenv
661 653 .LP
662 654 NIGHTLY_OPTIONS="-ACrlapDm"
663 655 .LP
664 656 export NIGHTLY_OPTIONS
665 657 .LP
666 658 # /opt/onbld/bin/nightly -i myenv
667 659 .PD
668 660 .LP
669 661 .SH SEE ALSO
670 662 .BR bldenv (1)
|
↓ open down ↓ |
229 lines elided |
↑ open up ↑ |
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX