On Fri, 4 Feb 2005, Starlink Software wrote:
> Module: tcl
> Status: failed
> Build Log: http://dev.starlink.ac.uk/build/SPARC-SOL9/logs/tcl.1107490659.log
Norman,
I've looked at this error quite closely and I am still mystified by it. I
don't see this on my test machine at Durham, but I can easily reproduce it
at RAL. The problem occurs in the install-manifest section (produced by
the STAR_SPECIAL_INSTALL_COMMAND macro) which seems to just throw an error
from some part with no clearly identifiable command and which may depend
on the current state of the directories that are being installed into (the
failure seems to depend on the existence of the /star/man directory for
instance).
So far the only work-arounds I've come up with are ignore the error (which
seems to have no ill effects) or, more interestingly, I can either remove
the following line:
exec 5>&-; \
or make sure that the install-manifest target is called with
SHELL=/bin/bash, rather than SHELL=/bin/sh (these two shells seem to be
mismatched in the Makefile, the main one is /bin/bash, but
install-manifest is forced to use /bin/sh).
After seeing all that I followed a hunch and tried changing the file
descriptor from 5 to 8, which also worked! I guess if this failed
consistently and on other platforms (it does look a lot like the error
under Tru64 UNIX, but I haven't looked at that closely) you might think
that the file description 5 was in use under certain conditions and
closing it caused an error, have you had any insights on any of this?
Cheers,
Peter.
|