#15045: ATLAS: multiple definition of `ATL_SetAtomicCount'
-------------------------------------------------+-------------------------
Reporter: jdemeyer | Owner:
Type: defect | Status:
Priority: blocker | needs_work
Component: packages: standard | Milestone: sage-5.12
Keywords: | Resolution:
Authors: Volker Braun | Merged in:
Report Upstream: Reported upstream. No | Reviewers:
feedback yet. | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
-------------------------------------------------+-------------------------
Changes (by jdemeyer):
* status: needs_review => needs_work
Comment:
Replying to [comment:17 vbraun]:
> Noted, but the ATLAS spkg has always been trying different ways to build
and falling back if they fail.
Those "different ways" only were about tuning parameters and CPU
instruction sets, right? Which is far less fundamental than static vs.
dynamic libraries.
Imagine we go with your solution and in the future somebody decides to
change the Sage build system or some package such that it only works for a
dynamic ATLAS library. Initial testing might reveal that everything works,
even though it doesn't work in case your ATLAS spkg decides to use static
libraries. This is what I want to avoid.
--
Ticket URL: <http://trac.sagemath.org/ticket/15045#comment:18>
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/groups/opt_out.
