These are chat archives for symengine/symengine

21st
Jan 2016
Isuru Fernando
@isuruf
Jan 21 2016 02:39
@porpoisepor, no. There's lots of features missing in Ruby wrappers.
porpoisepor
@porpoisepor
Jan 21 2016 14:00
Thanks
Ondřej Čertík
@certik
Jan 21 2016 16:01
@porpoisepor if you are interested in the Ruby support, we can help you implement any missing wrappers.
Ondřej Čertík
@certik
Jan 21 2016 16:09
@bcumming yes, as @Sumith1896 said, eventually we would like to have advanced features like ODE solvers, but for now we are concentrating on the basics to make them as fast as possible and make it work as a backend for SymPy and Sage, as well as for any C++ code (as well as Ruby or Julia and we can have more wrappers). Let us know what features you need that are missing. You can report them into our issues at github.
@isuruf, @rwst any objections against me creating a mailinglist for symengine? I think we have enough traffic that it would be useful, and most of the questions are symengine's specific, so do not really belong on the sympy list.
Ralf Stephan
@rwst
Jan 21 2016 16:11
@certik +1 go ahead, which host?
Sumith Kulal
@Sumith1896
Jan 21 2016 16:12
+1 from me too
Ondřej Čertík
@certik
Jan 21 2016 16:12
is there a better alternative to google groups?
their online interface kind of sucks, but overall I think they work pretty well. I don't want to maintain a server for it, so I want something online.
Isuru Fernando
@isuruf
Jan 21 2016 16:14
+1 for google groups
Ralf Stephan
@rwst
Jan 21 2016 16:14
Their digest and moderation is fine.
Isuru Fernando
@isuruf
Jan 21 2016 16:15
@abinashmeher999, I noticed that symengine is listed as a broken gem. https://github.com/SciRuby/sciruby/blob/master/gems.yml#L402
Ondřej Čertík
@certik
Jan 21 2016 16:17
@abinashmeher999 if you could fix that, that would be awesome. We can help.
Isuru Fernando
@isuruf
Jan 21 2016 16:20
@certik, we fixed the issues that were there. It's just a matter of updating symengine hash and checking with SciRuby people.
Ondřej Čertík
@certik
Jan 21 2016 16:26
@isuruf awesome.
@isuruf, @rwst, @Sumith1896 here is our new mailinglist: https://groups.google.com/forum/#!forum/symengine
We should add it to the README
Sumith Kulal
@Sumith1896
Jan 21 2016 16:27
I'll do that
Ondřej Čertík
@certik
Jan 21 2016 16:27
I am doing it
Sumith Kulal
@Sumith1896
Jan 21 2016 16:28
Oh okay :)
Ondřej Čertík
@certik
Jan 21 2016 16:29
See #775
Ondřej Čertík
@certik
Jan 21 2016 16:44
@bluescarni thanks for adding an LGPL license to Piranha.
Sumith Kulal
@Sumith1896
Jan 21 2016 16:54
Could somebody restart the appveyor build https://ci.appveyor.com/project/certik/symengine/build/699 ?
I can't do it and it's blocking #761
Ondřej Čertík
@certik
Jan 21 2016 16:58
I just restarted it. It looked like all tests passed, and that one failure was due to AppVeyor.
Sumith Kulal
@Sumith1896
Jan 21 2016 17:07
#748 needs a travis restart too
Thanks @certik for both :)
porpoisepor
@porpoisepor
Jan 21 2016 17:16
Are the tests working?
If I try to install symengine and then upon using ctest 20 out of 20 tests fail does this mean I did something wrong in the installation?
Ondřej Čertík
@certik
Jan 21 2016 17:17
@porpoisepor tests should definitely be working
can you post the log, and run the tests with ctest --output-on-failure
porpoisepor
@porpoisepor
Jan 21 2016 17:28

think I just realized I'm not supposed to run the tests in the build dir, all the test logs say Unable to find executable:

What is the default installation dir for symengine? (sorry I'm new to compilation / linux in general )

Isuru Fernando
@isuruf
Jan 21 2016 17:30
@porpoisepor, you are supposed to run the tests in the build dir. Unable to find executable error is there if either
  1. you are not running ctest from build dir
  2. make was interrupted before completion. In this case run make until completion
  3. building of tests were stopped with cmake -DBUILD_TESTS=no. In this case run cmake -DBUILD_TESTS=yes.
Default installation directory would be /usr/local/lib for library and /usr/local/include for headers
Ondřej Čertík
@certik
Jan 21 2016 17:33
Note that you do not need to install symengine in order to run tests. Just do make and run tests from the build directory.
porpoisepor
@porpoisepor
Jan 21 2016 17:44
Oh ok thank you all
Now it's working perfectly, turns out I had renamed a dir the other day and had forgotten about it
These logs are really handy