Opened 12 years ago

Closed 11 years ago

#7282 closed defect (invalid)

port jinja to install on cygwin

Reported by: was Owned by: tbd
Priority: major Milestone: sage-duplicate/invalid/wontfix
Component: porting: Cygwin Keywords:
Cc: Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges


Right now the jinja spkg segfaults when being installed on cygwin.

Change History (5)

comment:1 Changed 12 years ago by was

NOTE: I discovered that if I comment out the lines

#from hashlib import sha1
    #from hashlib import sha1
    #raise ImportError
#except ImportError:
#    from sha import new as sha1

in jinja/ then python build doesn't segfault, though installing does. However, I can copy the build/lib*/jinja directory over to site-packages by hand and it seems to work.

Similar remarks apply to Sphinx.

comment:2 Changed 12 years ago by mhansen

We really should try to make sure that there are no problems with hashlib since it's a very common module.

comment:3 Changed 12 years ago by mhansen

The problem occurs somewhere with the optional speedups extension. We can (temporarily) work around this by doing

python --without-speedups install

on Cygwin.

comment:4 Changed 12 years ago by mhansen

Also, once jinja2 is installed as above, Sphinx installs without a problem.

comment:5 Changed 11 years ago by mhansen

  • Milestone changed from sage-4.3.3 to sage-duplicate/invalid/wontfix
  • Report Upstream set to N/A
  • Resolution set to invalid
  • Status changed from new to closed

This currently builds fine with Cygwin 1.7

Note: See TracTickets for help on using tickets.