On Mon, Aug 4, 2014 at 6:17 AM, William A Stein <wst...@uw.edu> wrote:
> Hi,
>
> I installed Sage-6.3.beta6 on SageMathCloud, then installed a big list
> of optional packages, including cryptominisat. I was surprised when
> the next day a user reported that CryptoMiniSat didn't work, and when
> you attempt to use it, you see
>
> Run "install_package('cryptominisat')" to install it.
>
> I tried the above (as the owner of the sage install), and it did not
> fix the problem. What did fix the problem was typing "sage -b".
> So... it seems like somebody removed doing "sage -b" after installing
> optional packages from the build system (if it was ever there?).
> There were several other Cython modules that also weren't built.
Just to clarify -- this is exactly what wasn't built (not several
other modules):
Compiling sage/libs/coxeter3/coxeter.pyx because it changed.
Compiling sage/numerical/backends/coin_backend.pyx because it changed.
Compiling sage/sat/solvers/cryptominisat/cryptominisat.pyx because it changed.
Compiling sage/sat/solvers/cryptominisat/solverconf.pyx because it changed.
>
> Thoughts? Obviously, doing "sage -b" after installing standard
> packages wouldn't make sense, e.g, because "sage -b" wouldn't work.
>
> -- William
>
>
>
> --
> William Stein
> Professor of Mathematics
> University of Washington
> http://wstein.org
> wst...@uw.edu
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org
wst...@uw.edu
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
