The problem is that for one argument STAR_CHECK_PROGS if the application
can't be found, the buikld system sets it to be the name of the
application without a full path. ie it assumes that it will appear in the
path during the build and before it is needed.
This approach falls over with prohlp because it gets installed into
bindir/sst. Either this means that sst should be built early in the build
as a configure-dep or prohlp should be installed into bindir and not
bindir/sst. The former is currently problematic since that would imply
three quarters of all the libraries being build before the build starts!
The latter is the only way to go but is messy (It'd be cleaner if the IFC
files were installed into etc/ somewhere and an additional ADAM_IFL search
path compiled into PCS.
Tim
On Tue, 12 Oct 2004, Alasdair Allan wrote:
> For instance
>
> /bin/sh: line 1: prohlp: command not found
> /bin/sh: line 1: prohlp: command not found
> /bin/sh: line 1: prohlp: command not found
> /bin/sh: line 1: prohlp: command not found
> /bin/sh: line 1: prohlp: command not found
> /bin/sh: line 1: prohlp: command not found
> /bin/sh: line 1: prohlp: command not found
> /bin/sh: line 1: prohlp: command not found
> /bin/sh: line 1: prohlp: command not found
> /bin/sh: line 1: prohlp: command not found
> /bin/sh: line 1: prohlp: command not found
> /bin/sh: line 1: prohlp: command not found
> /bin/sh: line 1: prohlp: command not found
> /bin/sh: line 1: prohlp: command not found
> /bin/sh: line 1: prohlp: command not found
> /bin/sh: line 1: prohlp: command not found
> make[2]: *** [hdstools.hlp] Error 127
> make[1]: *** [all] Error 2
> make: *** [/h/jini/classic/manifests/hdstools] Error 2
> pinky{jini}:
>
> and
>
>
> current directory is /shaggy/jini/checkout/applications/kaprh/sun239_htx/
> ...
> make[2]: prohlp: Command not found
> make[2]: *** [kaprh.hlp] Error 127
> make[1]: *** [all-recursive] Error 1
> make: *** [/h/jini/classic/manifests/kaprh] Error 2
> shaggy{jini}:
>
> although it seems to be occuring in different places on my parallel
> builds (I've got three RH9 builds running simultaneously), which is
> all rather confusing.
>
> Al.
>
--
Tim Jenness
JAC software
http://www.jach.hawaii.edu/~timj
