Re: [Axiom-developer] gclcvs-2.7.0 and Axiom

[Stephen Wilson]

Camm Maguire <address@hidden> writes:

> Greetings, and thanks!  Will look at your tree....

Great!

> Mine just got this, in layer 18:
> 
> compiling QUATCAT.spad to QUATCAT.nrlib
> copying QUATCAT.nrlib to QUATCAT.o
> cp: cannot stat `/fix/t1/camm/axiom/int/algebra/QUATCAT.nrlib/code.o': No 
> such file or directory
> make[3]: *** [/fix/t1/camm/axiom/mnt/linux/algebra/QUATCAT.o] Error 1
> make[3]: Leaving directory `/fix/t1/camm/axiom/src/algebra'
> make[2]: *** [algebradir] Error 2
> make[2]: Leaving directory `/fix/t1/camm/axiom/src'
> make[1]: *** [srcdir] Error 2
> make[1]: Leaving directory `/fix/t1/camm/axiom'
> make: *** [all] Error 2

I do not recall the build failing at this particular point in the
past, but it is further along in the build than I can manage at the
moment (TREE.spad fails at layer 14 IIRC), so at the moment I am at a
loss to provide an explanation.

> How can I get a reproducible failing sequence of commands from failed
> make output?

Unfortunately, there is no way to see the explicit commands issued via
make.  However, when a build command fails, one can look at the file
./obj/tmp/trace which is created afresh after most commands issued via
make, and in general contain the output of the most recently failed
stanza.

In the case of algebra failures, a reasonable way to reproduce the state
is to issue from the root of the build tree:

  DAASE=./src/share ./obj/linux/bin/interpsys

  (1) -> )co ./int/algebra/QUATCAT.spad

This is effectively what the makefile invokes and gives a first hand
look at the failure.


Sincerely,
Steve


> 
> Take care,
> -- 
> Camm Maguire                                          address@hidden
> ==========================================================================
> "The earth is but one country, and mankind its citizens."  --  Baha'u'llah