On Tuesday, July 5, 2016 at 7:33:50 PM UTC+1, tdumont wrote:
>
> Le 04/07/2016 23:10, Francois Bissey a écrit :
> > I wouldn’t try to use one of these. Detecting blas/lapack automatically
> is
> > a fool’s errand. There are no standard naming scheme for the libraries
> > and distress can mess
Le 04/07/2016 23:10, Francois Bissey a écrit :
> I wouldn’t try to use one of these. Detecting blas/lapack automatically is
> a fool’s errand. There are no standard naming scheme for the libraries
> and distress can mess things up on top of it.
> The only safe way is to get the stuff needed to link
1.2.2-67 is ready.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googleg
Le mardi 5 juillet 2016 10:43:52 UTC+2, François a écrit :
>
>
> Han, I have looked at both giacpy and giacpy-sage now. They hardly
> have anything in common anymore.
> At least, it is not obvious from the repos.
>
> Given that the split is already that wide, would there be an objection
> to
> On 4/07/2016, at 22:17, Han Frederic wrote:
>
> I haven't gone through giacpy yet, but I don't like the fact there
> is a sage specific version. Something could be done to only have one
> source if my understanding of the issues and solution are correct.
>
> This need works and it could en
> On 5/07/2016, at 09:10, Francois Bissey
> wrote:
>
> I wouldn’t try to use one of these. Detecting blas/lapack automatically is
> a fool’s errand. There are no standard naming scheme for the libraries
> and distress can mess things up on top of it.
distress -> distros [thank you automatic sp
I wouldn’t try to use one of these. Detecting blas/lapack automatically is
a fool’s errand. There are no standard naming scheme for the libraries
and distress can mess things up on top of it.
The only safe way is to get the stuff needed to link on the command line.
You may want to add detection of
On Friday, July 1, 2016, Ralf Stephan wrote:
> On Wednesday, June 1, 2016 at 10:00:34 AM UTC+2, Ralf Stephan wrote:
>>
>> The giac and giacpy packages are now one year optional (#12375). Since
>> pynac-0.6.6 (#20742) has optional support for giac, and uses it to fix a
>> bug,
>> as well as a much
The giac and giacpy packages are now one year optional (#12375). Since
pynac-0.6.6 (#20742) has optional support for giac, and uses it to fix a
bug,
as well as a much faster GCD, I'm proposing to make the giac/giacpy packages
a standard part of Sage. In a recent thread we could also read about the
