On Fri, Apr 24, 2009 at 07:13:49PM +0200, Roland Mainz wrote:
> Casper.Dik at Sun.COM wrote:
> >
> > >Do you mean the OS/Net build environment should use /usr/bin/shcomp from
> > >the build machine and _not_ the "shcomp" binary from the "proto" area
> > >(which is the obvious case, otherwise libc, libast or libshell changes
> > >may bite you...) ?
> >
> > Neither, you need to build a *second* copy of shcomp: one which is linked
> > to the current system, but possibly using the ksh93 libraries; these would
> > typically be build twice (one "native" and one in the proto).
>
> Why do we need to build a 3rd copy (e.g. one in /usr/bin/shcomp, one in
> the proto area as ${ROOT}/usr/bin/shcomp and a 3rd one in the tools
> proto/ area) ?
Because the one in the tools area can run on the build system, yet
unlike the build system's /usr/bin/shcomp, the tools area version will
be built from the same source as the one in the proto area. This means
that if the build system's ksh93 is older than the ksh93 in the gate you
can still build the gate using the latest ksh93 for script compilation.
Nico
--
