#15045: ATLAS: multiple definition of `ATL_SetAtomicCount'
-------------------------------------------------+-------------------------
Reporter: jdemeyer | Owner:
Type: defect | Status:
Priority: blocker | needs_review
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:
-------------------------------------------------+-------------------------
Comment (by jdemeyer):
Replying to [comment:8 vbraun]:
> But IMHO we should work towards a more configurable solution that will
just fall back to reference / openblas as appropriate if atlas doesn't
build. And perhaps not build atlas by default if it takes too long. And
then static libraries would be a huge pain in the butt.
If you want to work towards that goal, then the problem on this ticket
must be fixed in a proper way anyway. I don't see how using shared
libraries "sometimes" is closer to the stated goal than "never" using
shared libraries.
I am particularly bothered that the choice is non-deterministic and
difficult to predict, so Sage builds on the same machine will be
substantially different (one with shared ATLAS and one with static ATLAS).
--
Ticket URL: <http://trac.sagemath.org/ticket/15045#comment:9>
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.
