I wrote:
...
> These 2 errors (sed [] imbalance, xxx not found) are repeated for each
> subdirectory.
>
> In devtools/bin/build there are some sed commands:
> .  absolute_base_dir=`echo ${full_src_dir} | sed "s#${src_dir}\\$##"`
> .  arg=`echo $1 | sed 's/^-E//'`
snip...

> and lots more.  How to I find which sed caused the error?

Well, there are smart and experienced folks that have helped out
and maybe that is the best way to find the errant sed command?

In the CI I could have turned on command tracing (HPCMDTRACE
variable).  I could have done an :ERRDUMP command.  Except if
OPTION NOHELP was specified, the CI would have echoed the bad
command with a caret under the bad parm (but not which file it was
in).  Are there similar tricks one can do in the shell?

Thanks,
  Jeff

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *