#9665: Make lcalc accessible as a library on OS X
----------------------------+-----------------------------------------------
Reporter: mpatel | Owner: tbd
Type: defect | Status: closed
Priority: blocker | Milestone: sage-4.5.2
Component: packages | Resolution: fixed
Keywords: | Author: Rishikesh
Upstream: N/A | Reviewer: Georg S. Weber
Merged: sage-4.5.2.rc1 | Work_issues:
----------------------------+-----------------------------------------------
Comment(by fbissey):
OK since I am redirected here.
Yes the lcalc spkg cleaning should happen in another ticket.
But does the lcalc wrapper in sage really need mpfr if lcalc
doesn't? From the new module_list.py:
{{{ Extension('sage.libs.lcalc.lcalc_Lfunction',
sources = ['sage/libs/lcalc/lcalc_Lfunction.pyx'],
libraries = ['m', 'ntl', 'mpfr', 'gmp', 'gmpxx',
'Lfunction', 'stdc++'],
include_dirs = [SAGE_ROOT + "/local/include/lcalc/"],
extra_compile_args=["-O3", "-ffast-math"],
language = 'c++'),
}}}
As a matter of fact I don't think it depends on gmp and gmpxx either.
Those are added when you use mpfr.
Actually at the moment Lfunction.so is never ever linked against mpfr,
gmp,
gmpxx and pari. Only the lcalc executable is. The same could be said for
ntl,
which isn't a dependency of lcalc at all.
So unless the wrapper itself needs any of these I suggest they should go.
Francois
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9665#comment:19>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
