New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cygwin: maxima does not build on cygwin, possibly due to ECL bug. #8269
Comments
comment:2
Even after upgrading to the latested released ECL (10.2.1),
we still have:
|
Author: Juan Jose Garcia-Ripoll, wstein |
comment:4
Juan-Jose had the following suggestion:
I tried this with the following new spkg: http://wstein.org/home/wstein/ports/cygwin/maxima-5.20.1.p1.spkg
The failure happens during the "make" step. |
comment:5
continuing...
|
comment:6
I was able to get Maxima to build in Cygwin with ECL 10.3.1 and the spkg at http://sage.math.washington.edu/home/mhansen/cygwin_port/maxima-5.20.1.p0.spkg . Everything builds correctly except building maxima as a library at the end:
All of the building commands run correctly, but there is no "maxima.fasb" file produced. |
comment:9
Although Maxima continue to not build consistently on Cygwin, neither on XP nor Win7, this bug is now vague and old enough that we should go to the more current tickets mentioned in the previous comment, which have information relevant to more current spkgs. In addition, it appears there was a fix of some kind which is now invalid due to other reasons, so this is really just too confusing now. To release manager: please close this ticket. |
Changed author from Juan Jose Garcia-Ripoll, wstein to none |
Reviewer: Karl-Dieter Crisman, Mike Hansen |
Trying to build the maxima-5.20.1.spkg fails on Cygwin. The error is
See this possibly very relevant thread for a discussion about this: http://groups.google.com/group/sage-devel/browse_thread/thread/cecd40138ed552b9
CC: @jdemeyer
Component: porting: Cygwin
Reviewer: Karl-Dieter Crisman, Mike Hansen
Issue created by migration from https://trac.sagemath.org/ticket/8269
The text was updated successfully, but these errors were encountered: