Opened 13 years ago

Closed 13 years ago

#1282 closed defect (fixed)

make flint.spkg depend on python

Reported by: mabshoff Owned by: mabshoff
Priority: major Milestone: sage-2.8.15
Component: packages: standard Keywords:
Cc: Merged in:
Authors: Reviewers:
Report Upstream: Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges


The thing to do is to change the sage build process so that building
FLINT depends on
having already built Python.    Then python-2.5.1 -- built by sage -- will get
used if you put
  #!/usr/bin/env python
at the top of a script or whatever.  I.e., it will be in your path.

I hadn't realized that building flint required Python, so we didn't
put that as a dependency
in the overall Sage makefile.




Change History (3)

comment:1 Changed 13 years ago by mabshoff

  • Status changed from new to assigned

comment:2 Changed 13 years ago by pdenapo

Script started on Mon Dec 3 14:08:30 2007 When trying to build sage-2.8.15 under Slackware Linux, the build broke with the following messages:

/sage/sage-2.8.14/spkg/build/flint-0.9-r1075.p1/src bash-3.1# make python fmpz_poly /usr/bin/python: /usr/bin/python: cannot execute binary file make: * [fmpz_poly-profile-tables.o] Error 126 bash-3.1# exit exit

Actually, I had a broken symlink /usr/bin/python (to python2.4) , but no python was really installed the system.

It seems that flint tries to use python from the system, instead of the version included in Sage.

comment:3 Changed 13 years ago by was

  • Resolution set to fixed
  • Status changed from assigned to closed

I made the 10 character change...

Note: See TracTickets for help on using tickets.