On Friday, October 5, 2012 5:05:10 PM UTC+2, kcrisman wrote:
>
>
>
> On Thursday, October 4, 2012 12:07:27 PM UTC-4, kcrisman wrote:
>>
>>
>> > 
>> > Should we continue this conversation in a new thread, or on 
>> sage-windows? 
>>
>> For now I'll leave it on sage-devel... though this is mainly for JP 
>> and/or Dima. 
>>
>>
> Other than the cvxopt issue, which I'm sure you're right about, Sage 
> builds!  First time in months for me.  And, for the first time in years...
>
> Testing that Sage starts...
> Yes, Sage starts. 
>
> Great! 

> !!!!!
>
> Still couldn't import maxima_lib when it tried to build doc (I only have 
> the p0 from #13324, so I guess I missed that I should use #9167), and then 
> it failed anyway with what appears to be a "need to rebase" error.  Still, 
> this is good news.
>
Yup, for the maxima_lib thingy you need the spkg from #9167.
The problem here is a collision between the main ecl library named ecl.dll 
and a dll produced by Sage with the same name.
We should definitely work with upstream and get something integrated there 
to follow the usual Cygwin naming scheme which would name the main ecl 
library cygecl-??.dll in bin/, and put an import library in lib/ while we 
are at it.

If you have some time it would be nice to test the autotools spkg at #13557.
I think it is fine on Cygwin now, but I cannot get it because of memory 
exhaustion (maybe BLODA, but it happens as well in safe mode, so maybe some 
bad interaction between Windows 7 and Cygwin and forks, either in Cygwin 
either in 7).

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to 
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.


Reply via email to