On Tue, 20 Mar 2007 14:34:48 +0100 I. Szczesniak wrote:
> On 3/20/07, Peter Memishian <peter.memishian at sun.com> wrote:
> > ... and that cannot be done by rebuilding "probe" from the checked-in
> > sources?
> This is dependent on the target operating system. probe.sh => probe
> may just be a copy on some targets but others may require a more
> complex process. Solaris just requires a plain copy but you don't
> include the Mamfiles which tell the users about this relationship.
> IMO you have two options: Either ship files which are generated during
> the ast-open build or ship the Mamfiles to instruct users how they can
> create the files themselves.
the { make pp } probe scripts are the same on all architectures
ksh integration will need the pp probe for msgcc l10n
the pp probe script is made by
cat src/cmd/INIT/C+probe src/lib/libpp/pp.probe > probe.sh
cp probe.sh probe
chmod +x probe
the make probe script (not used by the ksh integration) is made by
cat src/cmd/INIT/C+probe src/cmd/INIT/make.probe > probe.sh
cp probe.sh probe
chmod +x probe
both compiler probes share the same C+probe preamble
pathnames above are relative to the upstream src
-- Glenn Fowler -- AT&T Research, Florham Park NJ --
