On 2004 Dec 16 , at 06.11, Starlink Software wrote:
> Build Log:
> http://dev.starlink.ac.uk/build/DEBIAN-3.0r3_i386/logs/
> MakeWorld.1103167929.log
At the end of this is
> cd libraries/idi \
> && (make && make install) >make.log 2>make.log.err || { cat
> make.log.err; false; }
> make[1]: *** [IDI_ERR] Segmentation fault
> make[1]: *** Deleting file `IDI_ERR'
> make: ***
> [/home/rlspc0/cvsbuild/nightly-build/build/install/manifests/idi]
> Error 1
I'm not sure how to debug this. Looking at my local configured
checkout, the rule for IDI_ERR is nothing special:
IDI_ERR: idi_err.msg
$(MESSGEN) -F idi_err.msg
and messgen will have run for several of the libraries built before
IDI. So no clues there.
Is there anyway I can play about on this machine/OS? This is the
machine which has a bundle of OSs installed, and which is rebooted in
each in turn, isn't it?
If there were some way I could log on and start poking around the
configured checkout, after the Debian build had failed, that would be
very handy.
Norman
--
----------------------------------------------------------------------
Norman Gray : Physics & Astronomy, Glasgow University, UK
http://www.astro.gla.ac.uk/users/norman/ : www.starlink.ac.uk
|