polymake and other optional spkg

[William Stein]

Hi,

In case anybody cares about the optional Sage polymake spkg, I've
moved it from optional to experimental, since it doesn't work at all.
See below. Also, note that the fricas spkg no longer works (unless
the user has clisp systemwide) because we switched to ECL for our
lisp. I've tested and all other optional spkg's work on sage.math.

polymake-2.2.p5/SPKG.txt
Finished extraction
****************************************************
Host system
uname -a:
Linux sage.math.washington.edu 2.6.24-23-server #1 SMP Wed Apr 1
22:14:30 UTC 2009 x86_64 GNU/Linux
****************************************************
****************************************************
GCC Version
gcc -v
Using built-in specs.
Target: x86_64-linux-gnu
Configured with: ../src/configure -v
--enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr
--enable-shared --with-system-zlib --libexecdir=/usr/lib
--without-included-gettext --enable-threads=posix --enable-nls
--with-gxx-include-dir=/usr/include/c++/4.2 --program-suffix=-4.2
--enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc
--enable-mpfr --enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.2.4 (Ubuntu 4.2.4-1ubuntu3)
****************************************************
/bin/ls: cannot access gmp-*.spkg: No such file or directory
Using to build polymake
tar: /scratch/wstein/build/sage-4.0.2.alpha3/spkg/standard/.spkg:
Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error exit delayed from previous errors
The gmp.spkg seems to be broken - installs from binaries require that
you download the latest gmp.spkg

real 0m0.011s
user 0m0.000s
sys 0m0.010s
sage: An error occurred while installing polymake-2.2.p5
Please email sage-devel http://groups.google.com/group/sage-devel
explaining the problem and send the relevant part of
of /scratch/wstein/build/sage-4.0.2.alpha3/install.log. Describe your
computer, operating system, etc.
If you want to try to fix the problem, yourself *don't* just cd to
/scratch/wstein/build/sage-4.0.2.alpha3/spkg/build/polymake-2.2.p5 and
type 'make'.
Instead type "/scratch/wstein/build/sage-4.0.2.alpha3/sage -sh"
in order to set all environment variables correctly, then cd to
/scratch/wstein/build/sage-4.0.2.alpha3/spkg/build/polymake-2.2.p5
(When you are done debugging, you can type "exit" to leave the
subshell.)

--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org

[maxthemouse]

On Jun 14, 3:57 pm, William Stein <wst...@gmail.com> wrote:
> Hi,
>
> In case anybody cares about the optional Sage polymake spkg, I've
> moved it from optional to experimental, since it doesn't work at all.
>  See below.    Also, note that the fricas spkg no longer works (unless
> the user has clisp systemwide) because we switched to ECL for our
> lisp.  I've tested and all other optional spkg's work on sage.math.
>

Hi,
Is there a plan for fricas? Another thing that does not work is "sage -
lisp" which gave the clisp prompt. I found this rather convenient
since I could just use the clisp within sage. Is there any plan/
interest to switch the this lisp interface to ecl? Does ecl use
readline?

Cheers,
Adam

[William Stein]

On Sun, Jun 14, 2009 at 6:55 PM, maxthemouse<adamwe...@yahoo.com> wrote:
>
>
>
> On Jun 14, 3:57 pm, William Stein <wst...@gmail.com> wrote:
>> Hi,
>>
>> In case anybody cares about the optional Sage polymake spkg, I've
>> moved it from optional to experimental, since it doesn't work at all.
>>  See below.    Also, note that the fricas spkg no longer works (unless
>> the user has clisp systemwide) because we switched to ECL for our
>> lisp.  I've tested and all other optional spkg's work on sage.math.
>>
>
> Hi,
> Is there a plan for fricas?

I emailed the people (Waldeck Hebisch and Bill Page) who made the Fricas spkg,
and I really hope they will make an ECL version of it. However, if
you want to try
that would I'm sure be appreciated.

> Another thing that does not work is "sage -
> lisp" which gave the clisp prompt. I found this rather convenient
> since I could just use the clisp within sage. Is there any plan/
> interest to switch the this lisp interface to ecl? Does ecl use
> readline?

For now you can at least start sage then type

sage: !ecl

to start ecl. It appears to not make any use of ecl. I don't know if
this is just
a compilation problem or an ecl limitation.

The Sage <--> lisp interface already works fine:

sage: lisp.eval('(+ 2 3)')
'5'

I'm not sure why %gap works but not %lisp:

sage: %lisp
ERROR: Magic function `lisp` not found.
sage: %gap
--> Switching to Gap <--
gap:

That should be consider a bug.

OK, two tickets:

(1) make "sage -lisp" run ecl: http://trac.sagemath.org/sage_trac/ticket/6287

(2) make %lisp work and run ecl + readline mode:
http://trac.sagemath.org/sage_trac/ticket/6288

-- William

[Marshall Hampton]

I care about the polymake spkg, and I know a few users who do too. It
would be nice to fix it; the last time I tried to install it I got
some errors I didn't understand at all so I'm not sure what exactly
the problem is. Its probably out of date anyway, so it might be best
to start from scratch if it is to be fixed.

Although the current included polytope code is somewhat disjointed,
buggy, and incomplete, it is progressing and getting closer to
polymake's functionality. I think this actually makes the polymake
spkg more important since it helps clarify what functionality needs to
be added.

-M. Hampton

> Please email sage-develhttp://groups.google.com/group/sage-devel

[maxthemouse]

>
> > Another thing that does not work is "sage -
> > lisp" which gave the clisp prompt. I found this rather convenient
> > since I could just use the clisp within sage. Is there any plan/
> > interest to switch the this lisp interface to ecl? Does ecl use
> > readline?
>
> For now you can at least start sage then type
>
> sage: !ecl
>
> to start ecl.  It appears to not make any use of ecl.  I don't know if
> this is just
> a compilation problem or an ecl limitation.
>

Thanks, I forgot about that way to do it. The lack of readline makes
it rather unfriendly though. I am just a beginner with lisp myself.

> The Sage <--> lisp interface already works fine:
>
> sage: lisp.eval('(+ 2 3)')
> '5'
>

Using 4.0 and 4.0.1 I get a long traceback that ends with:
RuntimeError: Unable to start Lisp because the command 'clisp-
noreadline --silent -on-error abort' failed.

Sage was compiled from source on Scientific Linux 5.1. I don't have a
global clisp available though.
I figured that it was something that had just not been looked at yet
in the transition to ecl.

Adam

[William Stein]

On Mon, Jun 15, 2009 at 9:06 AM, maxthemouse<adamwe...@yahoo.com> wrote:
>
>
>>
>> > Another thing that does not work is "sage -
>> > lisp" which gave the clisp prompt. I found this rather convenient
>> > since I could just use the clisp within sage. Is there any plan/
>> > interest to switch the this lisp interface to ecl? Does ecl use
>> > readline?
>>
>> For now you can at least start sage then type
>>
>> sage: !ecl
>>
>> to start ecl.  It appears to not make any use of ecl.  I don't know if
>> this is just
>> a compilation problem or an ecl limitation.
>>
>
> Thanks, I forgot about that way to do it. The lack of readline makes
> it rather unfriendly though. I am just a beginner with lisp myself.
>
>> The Sage <--> lisp interface already works fine:
>>
>> sage: lisp.eval('(+ 2 3)')
>> '5'
>>
>
> Using 4.0 and 4.0.1 I get a long traceback that ends with:
> RuntimeError: Unable to start Lisp because the command 'clisp-
> noreadline --silent -on-error abort' failed.
>
> Sage was compiled from source on Scientific Linux 5.1. I don't have a
> global clisp available though.
> I figured that it was something that had just not been looked at yet
> in the transition to ecl.

No -- it's my fault. I was testing on an install that I upgraded, and
which still had clisp sitting around.

This is now

http://trac.sagemath.org/sage_trac/ticket/6294

I think we (=sage devel team) did a very bad job switching
from clisp to ecl. Sorry about the inconvenience.


-- William

>
> Adam
>
>> I'm not sure why %gap works but not %lisp:
>>
>> sage: %lisp
>> ERROR: Magic function `lisp` not found.
>> sage: %gap
>>   --> Switching to Gap <--
>> gap:
>>
>> That should be consider a bug.
>>
>> OK, two tickets:
>>
>>   (1) make "sage -lisp" run ecl:  http://trac.sagemath.org/sage_trac/ticket/6287
>>
>>   (2) make %lisp work and run ecl + readline mode:http://trac.sagemath.org/sage_trac/ticket/6288
>>
>>  -- William
> >
>

[William Stein]

On Mon, Jun 15, 2009 at 6:03 AM, Marshall Hampton<hamp...@gmail.com> wrote:
>
> I care about the polymake spkg, and I know a few users who do too.  It
> would be nice to fix it; the last time I tried to install it I got
> some errors I didn't understand at all so I'm not sure what exactly
> the problem is.  Its probably out of date anyway, so it might be best
> to start from scratch if it is to be fixed.

I hope somebody will try. The first time I ever heard of Polymake was
at Berkeley, where a lot of grad students wanted to use Polymake, but
couldn't build it (literally -- it was impossible because of lack of
RAM on their laptops). So I spent a day and got it to build into sage
with some hacks. It was somewhat painful. Polymake really is the
"Sage of polytopes", and is equally heavy. I hope somebody else will
do work and figure out how to build polymake into any sage well...