#9167: cygwin: importing sage.libs.ecl yields a "no such process" error
-------------------------------------------------------+--------------------
Reporter: was | Owner: tbd
Type: defect | Status:
needs_work
Priority: major | Milestone:
sage-5.3
Component: cygwin | Resolution:
Keywords: cygwin spkg ecl | Work issues:
Report Upstream: Reported upstream. No feedback yet. | Reviewers:
Authors: Jean-Pierre Flori | Merged in:
Dependencies: #13324 | Stopgaps:
-------------------------------------------------------+--------------------
Comment (by jpflori):
I don't agree with the point that libecl.dll.a cshould not be picked up by
the linker.
It is not necessary and you can directly link to cygecl.dll, that I agree
with, but it should be possible to go through libecl.dll.a as well.
Of course, there might be a problem with the produced libecl.dll.a, but
using import files should not be impossible.
Or then I don't understand how any piece of Sage can link with MPIR, MPFR
and any other library which uses libtool and which generates as well
import files and put them into SAGE_LOCAL/lib/ where they get picked up
before anything else.
And I don't think we have any piece of code which makes sure these dll.a
files are not used.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9167#comment:49>
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.
