Heads up for findunref users:
The -f flag to nightly now implies -0. That's the digit zero, and
it's the new flag to say "build the globalization package."
If you do not change your env file, you will see the following
warnings in your mail_msg:
> WARNING: the -f flag implies -0; enabling -0
>
> WARNING: the -0 flag requires that G11N_PKGDIR be set in the environment;
> ignoring -0
If you're building an ON repository, these messages are mostly
harmless. They will result in a false positive report of
usr/src/pkgdefs/SUNW0on/Makefile as unreferenced, which you can
resolve by setting G11N_PKGDIR; see below.
If you're building a non-ON repository, like SFW, then the messages
are completely harmless. If they irk you, you may silence them by
setting G11N_PKGDIR in your env file. See nightly(1) for details.
Heads up for folks wanting to build SUNW0on:
Per above, the nightly script has grown a new option: -0.
This option requires that the G11N_PKGDIR env variable be set.
Per the modified, default env files, this should generally be
${CODEMGR_WS}/usr/src/pkgdefs/SUNW0on
...though if you're using nightly.sh to build a consolidation other
than ON, you may want to change this, or leave it unset.
In general, it's a good idea to specify -0 when you specify -p. This
will cause the globalization package to be built. Previously, that
only happened if you did "bldenv env ; cd ${SRC}/pkgdefs/SUNW0on ;
dmake install" after your nightly build.
--Mark
