#17635: Update Givaro, FFLAS-FFPACK and LinBox
-------------------------------------+-------------------------------------
       Reporter:  jpflori            |        Owner:
           Type:  enhancement        |       Status:  new
       Priority:  major              |    Milestone:  sage-6.8
      Component:  packages:          |   Resolution:
  standard                           |    Merged in:
       Keywords:                     |    Reviewers:
        Authors:                     |  Work issues:
Report Upstream:  N/A                |       Commit:
         Branch:                     |  fb16751ee2a275d55bef8824ee606fdd98f817f8
  u/cpernet/givaro_fflasffpack_linbox|     Stopgaps:
   Dependencies:  #19298             |
-------------------------------------+-------------------------------------

Comment (by jdemeyer):

 This is still not quite what I meant.

 For example, why does
 `src/sage/rings/polynomial/multi_polynomial_ideal_libsingular.pxd` need
 `GIVARO_CFLAGS`? Looking at that file, there is ''nothing'' related to
 givaro.

 I assume you added `GIVARO_CFLAGS` because it still somehow indirectly
 includes Givaro code. But then you should add `GIVARO_CFLAGS` in the place
 where the Givaro headers are actually included and Cython's dependency
 tracking should pick it up.

 See again the `GSL_LIBRARIES` example: I don't add `GSL_LIBRARIES` to
 every module which somehow indirectly uses GSL, only where the library
 functions are actually declared.

--
Ticket URL: <http://trac.sagemath.org/ticket/17635#comment:25>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to