OpenSolaris

Flag Day: Tools update (6785284) can cause nightly/check_rtime mismatch

Date: Wed, 11 Feb 2009 09:59:15 -0700
From: Ali Bahrami <Ali.Bahrami at sun dot com>
To: onnv-gate at onnv dot eng dot sun dot com, on-all at eng dot sun dot com
Subject: Flag Day: Tools update (6785284) can cause nightly/check_rtime mismatch

My putback of

     6785284 Mapfile versioning rules need to be more visible to gatelings

is a flag day for those with preexisting workspaces that have not
pulled this change. You will see an error in the report from the
nightly script if all of the following are true:

     - Your build machine has been updated with the new version of
       the SUNWonbld build tools resulting from 6785284.

     - Your workspace has not been updated to contain the fix
       for 6785284.

     - You execute the copy of the nightly script supplied by the
       build machine via PATH, rather than the copy found in your
       workspace.

     - You use the -r option to nightly to check ELF attributes

     - You do not use the +t option to nightly, which disables
       use of the tools contained in the workspace.

If all of the above hold, you will see the following in the
report email from nightly:

     ==== Check ELF runtime attributes ====

	[-a]		process all files (ignore any exception lists)
	[-d dir]	establish dependencies from under directory
	[-i]		produce dynamic table entry information
	[-m]		process mcs(1) comments
	[-o]		produce one-liner output (prefixed with pathname)
	[-s]		process .stab and .symtab entries
     Unknown option: v
     usage: check_rtime [-a] [-d depdir] [-m] [-o] [-s] file | dir, ...

6785284 adds a new option to check_rtime (-v), and modifies nightly to use
it. In the situation described above, the new version of nightly ends up
calling an old version of check_rtime.

You can avoid the above by taking any one of the following steps. I list
them in rough order of preference,
with the best option first:

     - Update your workspace.

     - Invoke nightly from your workspace, rather than the version
       found via PATH:
         % bldenv env.file
         % cd usr/src/tools/scripts
         % dmake nightly
         % exit ; # leave bldenv shell
         % $SRC/tools/scripts/nightly ...

     - Use the +t option to nightly. This causes it to completely
       ignore the tools in your workspace and use the build server
       supplied tools for everything.

     - Don't upgrade the tools on your build server until your
       workspaces have pulled the changes from 6785284.

     - Don't specify the -r option to nightly

I apologize for the inconvenience.

- Ali