Ticket #1125 (closed defect: fixed)

Opened 6 years ago

Last modified 6 years ago

[with spkg] cvxopt fix completely breaks building Sage with gfortran

Reported by: was Owned by: was
Priority: blocker Milestone: sage-2.8.13
Component: packages: standard Keywords:
Cc: Work issues:
Report Upstream: Reviewers:
Authors: Merged in:
Dependencies: Stopgaps:

Description

> 
> Compiling from source using gcc-4.2.2, I get
> 
> ***
> x86-Linux, ia64-Linux
> ***
> While compiling cvxopt-0.8.2.p4, I get
> 
> gcc -pthread -shared build/temp.linux-i686-2.5/C/base.o
> build/temp.linux-i686-2.5/C/dense.o
> build/temp.linux-i686-2.5/C/sparse.o
> -L/home/kate/sage/sage-2.8.12-x86-Linux/local/lib
> -L/home/kate/sage/sage-2.8.12-x86-Linux/local/lib/gcc-lib/i686-pc-linux-gnu/4.0.3
> -lm -llapack -lblas -lf95 -o build/lib.linux-i686-2.5/cvxopt/base.so
> /usr/local/binutils-2.17/x86-Linux-gcc-4.1.1/bin/ld: cannot find -lf95

That's because you're using gfortran.  Evidently Josh's fix for cvxopt not fully working
fails for people using gfortran.  I'll open a trac ticket. 

This either has to be properly fixed, or cvxopt has to be removed or something. We need to make sure we fully support using gfortran. Perhaps we should just completely switch to using gfortran and make having gfortran installed a requirement for building sage. Tempting.

Change History

comment:1 Changed 6 years ago by was

  • Priority changed from critical to blocker

comment:2 Changed 6 years ago by mabshoff

  • Summary changed from cvxopt fix completely breaks building Sage with gfortran to [with spkg] cvxopt fix completely breaks building Sage with gfortran

Waiting on feedbackk from Kate, but there is a new spkg by Josh:

 http://sage.math.washington.edu/home/jkantor/spkgs/cvxopt-0.8.2.p5.spkg

Cheers,

Michael

comment:3 Changed 6 years ago by mabshoff

  • Milestone changed from sage-2.9 to sage-2.8.13

comment:4 Changed 6 years ago by jkantor

The spkg in 1161 incorporates the fix for this and also upgrades cvxopt to a newer version.

comment:5 Changed 6 years ago by mabshoff

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

superseded by #1161, which also contains this fix.

Note: See TracTickets for help on using tickets.