Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

So, the compilation process worked within my /home directory. However, after about an hour I got a real error this time:

***************************************************************
Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make all-start'):

* package: openblas-0.2.20.p2
  log file: /home/matthias/sage-8.4/logs/pkgs/openblas-0.2.20.p2.log
  build directory: /home/matthias/sage-8.4/local/var/tmp/sage/build/openblas-0.2.20.p2

The build directory may contain configuration files and other potentially
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.

Makefile:31 : la recette pour la cible « all-start » a échouée
make[1]: *** [all-start] Erreur 1
make[1] : on quitte le répertoire « /home/matthias/sage-8.4 »
Makefile:13 : la recette pour la cible « all » a échouée
make: *** [all] Erreur 2

This seems to be about the openblas package. There is the mentioned log.

So, at this point, I don't care about starting a new compilation from scratch, nevertheless, 1) Can I resume a failed compilation after a possible fix of what's amiss? 2) Why is that happening? Is there any risk some other package might do the same?

Thank you

(this was about to be a comment but it's too long)

So, the compilation process worked within my /home directory. However, after about an hour I got a real error this time:

***************************************************************
Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make all-start'):

* package: openblas-0.2.20.p2
  log file: /home/matthias/sage-8.4/logs/pkgs/openblas-0.2.20.p2.log
  build directory: /home/matthias/sage-8.4/local/var/tmp/sage/build/openblas-0.2.20.p2

The build directory may contain configuration files and other potentially
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.

Makefile:31 : la recette pour la cible « all-start » a échouée
make[1]: *** [all-start] Erreur 1
make[1] : on quitte le répertoire « /home/matthias/sage-8.4 »
Makefile:13 : la recette pour la cible « all » a échouée
make: *** [all] Erreur 2

This seems to be about the openblas package. There is the mentioned log.

So, at this point, I don't care about starting a new compilation from scratch, nevertheless, 1) Can I resume a failed compilation after a possible fix of what's amiss? 2) Why is that happening? Is there any risk some other package might do the same?

Thank you

(this was about to be a comment but it's too long)

So, the compilation process worked within my /home directory. However, after about an hour I got a real error this time:

***************************************************************
Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make all-start'):

* package: openblas-0.2.20.p2
  log file: /home/matthias/sage-8.4/logs/pkgs/openblas-0.2.20.p2.log
  build directory: /home/matthias/sage-8.4/local/var/tmp/sage/build/openblas-0.2.20.p2

The build directory may contain configuration files and other potentially
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.

Makefile:31 : la recette pour la cible « all-start » a échouée
make[1]: *** [all-start] Erreur 1
make[1] : on quitte le répertoire « /home/matthias/sage-8.4 »
Makefile:13 : la recette pour la cible « all » a échouée
make: *** [all] Erreur 2

This seems to be about the openblas package. There is the mentioned log.

So, at this point, I don't care about starting a new compilation from scratch, nevertheless, 1) Can I resume a failed compilation after a possible fix of what's amiss? 2) Why is that happening? Is there any risk some other package might do the same?

Thank you

(this was about to be a comment but it's too long)

So, the compilation process worked within my /home directory. However, after about an hour I got a real error this time:

***************************************************************
Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make all-start'):

* package: openblas-0.2.20.p2
  log file: /home/matthias/sage-8.4/logs/pkgs/openblas-0.2.20.p2.log
  build directory: /home/matthias/sage-8.4/local/var/tmp/sage/build/openblas-0.2.20.p2

The build directory may contain configuration files and other potentially
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.

Makefile:31 : la recette pour la cible « all-start » a échouée
make[1]: *** [all-start] Erreur 1
make[1] : on quitte le répertoire « /home/matthias/sage-8.4 »
Makefile:13 : la recette pour la cible « all » a échouée
make: *** [all] Erreur 2

There Here is the mentioned log.

So, at this point, I don't care about starting a new compilation from scratch, nevertheless, 1) Can I resume a failed compilation after a possible fix of what's amiss? 2) Why is that happening? Is there any risk some other package might do the same?

Thank you

(this was about meant to be a comment but it's too long)

So, the compilation process worked within my /home directory. However, after about an hour I got a real error this time:

***************************************************************
Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make all-start'):

* package: openblas-0.2.20.p2
  log file: /home/matthias/sage-8.4/logs/pkgs/openblas-0.2.20.p2.log
  build directory: /home/matthias/sage-8.4/local/var/tmp/sage/build/openblas-0.2.20.p2

The build directory may contain configuration files and other potentially
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.

Makefile:31 : la recette pour la cible « all-start » a échouée
make[1]: *** [all-start] Erreur 1
make[1] : on quitte le répertoire « /home/matthias/sage-8.4 »
Makefile:13 : la recette pour la cible « all » a échouée
make: *** [all] Erreur 2

Here is the mentioned log.

So, at this point, I don't care about starting a new compilation from scratch, nevertheless, 1) Can I resume a failed compilation after a possible fix of what's amiss? 2) Why is that happening? Is there any risk some other package might do the same?

Thank you

(this was meant to be a comment but it's too long)

So, the compilation process worked within my /home directory. However, after about an hour I got a real error this time:

***************************************************************
Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make all-start'):

* package: openblas-0.2.20.p2
  log file: /home/matthias/sage-8.4/logs/pkgs/openblas-0.2.20.p2.log
  build directory: /home/matthias/sage-8.4/local/var/tmp/sage/build/openblas-0.2.20.p2

The build directory may contain configuration files and other potentially
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.

Makefile:31 : la recette pour la cible « all-start » a échouée
make[1]: *** [all-start] Erreur 1
make[1] : on quitte le répertoire « /home/matthias/sage-8.4 »
Makefile:13 : la recette pour la cible « all » a échouée
make: *** [all] Erreur 2

Here is the mentioned log.

So, at this point, I don't care about mind starting a new compilation from scratch, nevertheless, 1) Can I resume a failed compilation after a possible fix of what's amiss? 2) Why is that happening? Is there any risk some other package might do the same?

Thank you