On Thu, 3 Mar 2005, Starlink Software wrote:
> Main URL: http://dev.starlink.ac.uk/build/TRU64-ALPHA/
>
> Module: kaprh
> Status: failed
> Build Log: http://dev.starlink.ac.uk/build/TRU64-ALPHA/logs/kaprh.1109827654.log
>
> Module: daophot
> Status: failed
> Build Log: http://dev.starlink.ac.uk/build/TRU64-ALPHA/logs/daophot.1109827654.log
>
> Module: pisa
> Status: failed
> Build Log: http://dev.starlink.ac.uk/build/TRU64-ALPHA/logs/pisa.1109827654.log
>
> Module: MakeWorld
> Status: failed
> Build Log: http://dev.starlink.ac.uk/build/TRU64-ALPHA/logs/MakeWorld.1109827654.log
>
> Module: atools
> Status: failed
> Build Log: http://dev.starlink.ac.uk/build/TRU64-ALPHA/logs/atools.1109827654.log
>
> Module: kappa
> Status: failed
> Build Log: http://dev.starlink.ac.uk/build/TRU64-ALPHA/logs/kappa.1109827654.log
>
> Module: photom
> Status: failed
> Build Log: http://dev.starlink.ac.uk/build/TRU64-ALPHA/logs/photom.1109827654.log
>
> Module: extreme
> Status: failed
> Build Log: http://dev.starlink.ac.uk/build/TRU64-ALPHA/logs/extreme.1109827654.log
>
> Module: echomop
> Status: failed
> Build Log: http://dev.starlink.ac.uk/build/TRU64-ALPHA/logs/echomop.1109827654.log
>
> Module: esp
> Status: failed
> Build Log: http://dev.starlink.ac.uk/build/TRU64-ALPHA/logs/esp.1109827654.log
>
> Module: polpack
> Status: failed
> Build Log: http://dev.starlink.ac.uk/build/TRU64-ALPHA/logs/polpack.1109827654.log
>
> Module: pongo
> Status: failed
> Build Log: http://dev.starlink.ac.uk/build/TRU64-ALPHA/logs/pongo.1109827654.log
>
> Module: figaro
> Status: failed
> Build Log: http://dev.starlink.ac.uk/build/TRU64-ALPHA/logs/figaro.1109827654.log
>
> Module: sgmlkit
> Status: failed
> Build Log: http://dev.starlink.ac.uk/build/TRU64-ALPHA/logs/sgmlkit.1109827654.log
That's good to see again. Except for extreme and sgmlkit and the very odd
MakeWorld these match the same sort of problems that came up in Debian and
Solaris yesterday and x86_64 this morning (i.e missing AGI link
dependencies).
Steve,
I'll try to have a look at those autobuild.conf files and see how it
all looks in reality.
Cheers,
Peter.
|