Here's the absurd way I got my sage-4.4.3 install to fork.
Anyways, I did the following:
(0) Read about rebasing: /usr/share/doc/Cygwin/rebase-3.0.1.README
(1) Shutdown all cygwin processes using the task manager
(2) Using command.exe run c:\cygwin\bin\ash then
/bin/rebaseall -v
which didn't help at all since it only rebase /usr/.
(3) Tried Gary Zablackis's 2005 script, but by hand:
cd /home/wstein/sage-4.4.3/
/bin/find -name *.dll > Sage-dlls.lst
/bin/rebaseall -v -T Sage-dlls.lst
(4) The above failed with an error rebasing libpython.dll. So I
deleted the libpython.dll line from Sage-dlls.lst, then
again did
/bin/rebaseall -v -T Sage-dlls.lst
(5) This appeared to work... but Sage still did *not* fork. The
following popped up when
trying to fork in Sage: local/lib/libcurvesntl.dll
So, I edited Sage-dlls.lst, and deleted everything *before* the
libcurvesntl.dll line. Then I did
/bin/rebaseall -v -T Sage-dlls.lst
and amazingly after this forking with Sage works, as illustrated in
the screenshots.
---
Here's my build notes to go from stock sage-4.4.3 to something that I
built under Cygwin and can fully use:
1. Put the following four spkg's in place of the ones that are in
spkg/standard:
boehm_gc-7.1.p4.spkg ecl-10.4.1.spkg libpng-1.2.35.p2.spkg maxima-5.21.0.spkg
I put these at http://sage.math.washington.edu/home/wstein/patches/sage-cygwin-4.4.3.tar
temporarily, for convenience.
2. don't worry about cvxopt, which doesn't build, and is the last
thing. The build fails, but we just ignore it.
3. Sage doesn't start. Using "cygcheck" on problemative dll, we find
that a fix is to copy
libntl.dll.a to libntl.dll
in SAGE_ROOT/local/lib/
4. Then sage starts up.
* But it can't fork. We have to rebase. See above.
---
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org
I put a tarball of sage-4.4.3 built as below for cygwin, and the complete output
of "sage -t" on it at
http://sage.math.washington.edu/home/wstein/binaries/cygwin/
Thus if you want to try running sage-4.4.3 on Windows, this is an easy
way to try.
William
I've updated
http://trac.sagemath.org/sage_trac/wiki/CygwinPort
so it lists most of the problems with *using* (not building) Sage on
Cygwin that were uncovered by doctesting, along with individual
tickets for each problem.
-- William
I think this has nothing to do with rebasing. I think you need to
install some
Cygwin library packages, maybe openssl...?
William
> --
> You received this message because you are subscribed to the Google Groups "sage-windows" group.
> To post to this group, send email to sage-w...@googlegroups.com.
> To unsubscribe from this group, send email to sage-windows...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/sage-windows?hl=en.
---------- Forwarded message ----------
From: Andrew Trapani <andrew...@gmail.com>
Date: Wed, Jan 19, 2011 at 1:29 PM
Subject: Re: rebasing: I got it to work -- sage-4.4.3 under Cygwin
To: William Stein <wst...@gmail.com>
I found a very easy to reproduce bug using the maxima function solve:
http://www.sagemath.org/doc/tutorial/tour_algebra.html
x = var('x')
solve(x^2 + 3*x + 2, x)
It starts up maxima, solves it, but then when I save and quit, the
maxima process is still running. A process leak.
Every time I reload this worksheet and re-run the solve function, it
starts a new maxima process which stays connected until I save/discard
and quit the worksheet.
I updated cygwin today, 1.7.1-1, and updated all the libraries,
restarted.
Another bug, potentially solved,
Before updating I tried it and I was getting the associated python
process with a worksheet wouldn't necessarily get killed when I save/
discard and quit from this worksheet. This would eventually cause me
to be unable to load any worksheets until I manually kill these python
processes.
After updating, I haven't been able to reproduce this worksheet
process leak. It used to be very easy to reproduce, by just opening
and closing worksheets randomly, eventually (a minute or two) it would
have a process leak. It may be the update to cygwin has solved, or
partially solved, the worksheet process leak.
Still looking forward to future work on windows Sage.
Andrew
> > I put these athttp://sage.math.washington.edu/home/wstein/patches/sage-cygwin-4.4.3...
> > temporarily, for convenience.
>
> > 2. don't worry about cvxopt, which doesn't build, and is the last
> > thing. The build fails, but we just ignore it.
>
> > 3. Sage doesn't start. Using "cygcheck" on problemative dll, we find
> > that a fix is to copy
>
> > libntl.dll.a to libntl.dll
>
> > in SAGE_ROOT/local/lib/
>
> > 4. Then sage starts up.
>
> > * But it can't fork. We have to rebase. See above.
>
> > ---
>
> > --
> > William Stein
> > Professor of Mathematics
> > University of Washington
> >http://wstein.org
>
> --
> William Stein
> Professor of Mathematics
> University of Washingtonhttp://wstein.org
Hi,I put a tarball of sage-4.4.3 built as below for cygwin, and the complete output
of "sage -t" on it athttp://sage.math.washington.edu/home/wstein/binaries/cygwin/
Thus if you want to try running sage-4.4.3 on Windows, this is an easy
way to try.William
On Sun, Jun 6, 2010 at 2:37 AM, William Stein <wst...@gmail.com> wrote:
> Hi Mike (cc: Sage Windows)
>
> Here's the absurd way I got my sage-4.4.3 install to fork.
> Anyways, I did the following:
>
> (0) Read about rebasing: /usr/share/doc/Cygwin/rebase-3.0.1.README
>
> (1) Shutdown all cygwin processes using the task manager
>
> (2) Using command.exe run c:\cygwin\bin\ash then
>
> /bin/rebaseall -v
>
> which didn't help at all since it only rebase /usr/.
>
> (3) Tried Gary Zablackis's 2005 script, but by hand:
>
> cd /home/wstein/sage-4.4.3/
> /bin/find -name *.dll > Sage-dlls.lst
> /bin/rebaseall -v -T Sage-dlls.lst
>
> (4) The above failed with an error rebasing libpython.dll. So I