Re: [sage-devel] Re: talk
Indeed, that link is no longer valid. Please visit this one instead: https://tinyurl.com/yac6cyzg On Tue, Sep 4, 2018 at 7:48 PM, saad khalid wrote: > Hello: > > The link seems to be broken, I was hoping to take a second look at some of > the items on the wishlist. is there any way you could repost it? Thank you. > > -Saad > > On Tuesday, July 24, 2018 at 3:18:32 PM UTC-4, William wrote: >> >> Hi, >> >> I just wrote a short talk that I'm about to give at ICMS 2018 about a >> sort of Sage status report and wishlist: >> >> https://goo.gl/qNycb3 >> >> -- >> William (http://wstein.org) > > -- > 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@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- William (http://wstein.org) -- 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@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: talk
Hello: The link seems to be broken, I was hoping to take a second look at some of the items on the wishlist. is there any way you could repost it? Thank you. -Saad On Tuesday, July 24, 2018 at 3:18:32 PM UTC-4, William wrote: > > Hi, > > I just wrote a short talk that I'm about to give at ICMS 2018 about a > sort of Sage status report and wishlist: > > https://goo.gl/qNycb3 > > -- > William (http://wstein.org) > -- 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@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Persistent homology software
If anyone with topological interests wants a new project, take a look at incorporating these into Sage: - Ripser, "a lean C++ code for the computation of Vietoris–Rips persistence barcodes",http://ripser.org - Flagser, "Computing homology of directed flag complexes" (based on ripser), https://github.com/luetge/flagser -- Share and Enjoy, John -- 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@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] r-3.4.4.p0 configure/install error
Wow! That did the trick!! Thanks for taking those guesses :) Best, Nagesh On Tue, Sep 4, 2018 at 3:25 PM John H Palmieri wrote: > I am not an expert in configure scripts, but it looks to me as though the > next thing in R's configure script deals with java. Maybe java is broken on > your system badly enough that it halts the configure script? You could try > this: > > - copy the flies java and javac from SAGE_ROOT/build/pkgs/r/patches/ to > SAGE_ROOT/local/bin. This installs intentionally "broken" versions of java > and javac, to prevent any system versions from interfering with R's > installation process. > - run 'make r' (which will try to install R). > - then delete the files java and javac from SAGE_ROOT/local/bin. > > I'm really just taking guesses, though. > > John > > > On Tuesday, September 4, 2018 at 12:40:38 PM UTC-7, Nagesh Adluru wrote: >> >> Hi Dima and John, >> >> I got the libstd++-static installed. I did not use screen this time. I am >> not sure how to make "check ...static libraries" to yes. The gcc, g++ and >> gfortran are all version 7.3.1 20180303 (Red Hat 7.3.1-5). >> >> I am still getting the error for r. I am attaching the fresh log again >> just in case. Also I was thinking, the latest version of R available is >> r.3.5.1 and sage is trying to install r.3.4.4. Would upgrading it to >> r.3.5.1 resolve this mysterious issue? >> >> Thanks so much for your insights and help! >> Sincerely, >> Nagesh >> On Mon, Sep 3, 2018 at 5:49 PM Nagesh Adluru wrote: >> >>> 1) I realized recently that libstd++-static is missing. I will try to >>> get those and also try to make "checkstatic libraries" to yes for >>> gfortran. >>> 2) I will try without screen just to check Dima's hypothesis. >>> 3) Thanks for sharing your input about paperconf, John! >>> >>> I will report back once I try these. >>> Thanks so much everyone! >>> Best, >>> Nagesh >>> >>> On Mon, Sep 3, 2018 at 5:17 PM John H Palmieri >>> wrote: >>> On my OS X machine, I do not have paperconf, and R builds just fine. I wonder if screen is getting in the way somehow. Can you try without using it? (According to the log file, gfortran seems to be there. There is no working ObjC++ compiler, but I don't think that should be an issue, right?) On Monday, September 3, 2018 at 2:33:22 PM UTC-7, Dima Pasechnik wrote: > > you do have gfortran installed, right? > (usually R is one of the last packages to be built, but perhaps you > overlooked some errors) > > The R install log after paperconf would go as follows: > > ... > checking for lpr... lpr > checking for paperconf... /usr/bin/paperconf > checking whether we are using the GNU Fortran compiler... yes > checking whether gfortran accepts -g... yes > checking if libtool supports shared libraries... yes > checking whether to build shared libraries... yes > checking whether to build static libraries... no > ... > > and so I suspect that it misreports a fortran error... > > > > On Mon, Sep 3, 2018 at 11:52 PM Nagesh Adluru > wrote: > > > > It is bash and > > the output of echo $SHELL is /bin/bash > > > > > > > > On Mon, Sep 3, 2018 at 3:44 PM Dima Pasechnik > wrote: > >> > >> looks puzzling. > >> What is your default shell? > >> If it is not bash, then there might be strange problems like this. > What is the output of > >> > >> echo $SHELL > >> > >> > >> > >> On Mon, 3 Sep 2018, 19:48 Nagesh Adluru, > wrote: > >>> > >>> Hi Dima, > >>> > >>> I am also getting the output letter just like in your case. It is > not crashing. So what would you think is the problem? > >>> > >>> Also thanks for clarifying about screen! > >>> > >>> Thanks so much. > >>> Nagesh > >>> > >>> On Mon, Sep 3, 2018 at 5:03 AM Dima Pasechnik > wrote: > > On Sun, Sep 2, 2018 at 11:20 PM Nagesh Adluru < > nagesh...@gmail.com> wrote: > > > > Hi David, > > > > Thanks for sharing that insight. I did install the anaconda in > between for a different purpose which explains the new problem with > libcurl > that I did not have before the libpaper issue. Based on your advice I > removed anaconda from the path and I did a full make distclean and > reinstall and now the libcurl is gone but it still errors after paperconf > message (log attached) even though we have libpaper installed (screenshot > attached). > > Please let me know what should I try next since libcurl seems > no longer to be a problem and libpaper is installed! > > > what is the output of 'paperconf' ? > Could you try running paperconf at shell prompt, to see if it > outputs > anything meaningful, e.g. for me it > outputs 'letter'. It looks as if it
Re: [sage-devel] r-3.4.4.p0 configure/install error
I am not an expert in configure scripts, but it looks to me as though the next thing in R's configure script deals with java. Maybe java is broken on your system badly enough that it halts the configure script? You could try this: - copy the flies java and javac from SAGE_ROOT/build/pkgs/r/patches/ to SAGE_ROOT/local/bin. This installs intentionally "broken" versions of java and javac, to prevent any system versions from interfering with R's installation process. - run 'make r' (which will try to install R). - then delete the files java and javac from SAGE_ROOT/local/bin. I'm really just taking guesses, though. John On Tuesday, September 4, 2018 at 12:40:38 PM UTC-7, Nagesh Adluru wrote: > > Hi Dima and John, > > I got the libstd++-static installed. I did not use screen this time. I am > not sure how to make "check ...static libraries" to yes. The gcc, g++ and > gfortran are all version 7.3.1 20180303 (Red Hat 7.3.1-5). > > I am still getting the error for r. I am attaching the fresh log again > just in case. Also I was thinking, the latest version of R available is > r.3.5.1 and sage is trying to install r.3.4.4. Would upgrading it to > r.3.5.1 resolve this mysterious issue? > > Thanks so much for your insights and help! > Sincerely, > Nagesh > On Mon, Sep 3, 2018 at 5:49 PM Nagesh Adluru > wrote: > >> 1) I realized recently that libstd++-static is missing. I will try to get >> those and also try to make "checkstatic libraries" to yes for gfortran. >> 2) I will try without screen just to check Dima's hypothesis. >> 3) Thanks for sharing your input about paperconf, John! >> >> I will report back once I try these. >> Thanks so much everyone! >> Best, >> Nagesh >> >> On Mon, Sep 3, 2018 at 5:17 PM John H Palmieri > > wrote: >> >>> On my OS X machine, I do not have paperconf, and R builds just fine. I >>> wonder if screen is getting in the way somehow. Can you try without using >>> it? >>> >>> (According to the log file, gfortran seems to be there. There is no >>> working ObjC++ compiler, but I don't think that should be an issue, right?) >>> >>> >>> >>> On Monday, September 3, 2018 at 2:33:22 PM UTC-7, Dima Pasechnik wrote: you do have gfortran installed, right? (usually R is one of the last packages to be built, but perhaps you overlooked some errors) The R install log after paperconf would go as follows: ... checking for lpr... lpr checking for paperconf... /usr/bin/paperconf checking whether we are using the GNU Fortran compiler... yes checking whether gfortran accepts -g... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no ... and so I suspect that it misreports a fortran error... On Mon, Sep 3, 2018 at 11:52 PM Nagesh Adluru wrote: > > It is bash and > the output of echo $SHELL is /bin/bash > > > > On Mon, Sep 3, 2018 at 3:44 PM Dima Pasechnik wrote: >> >> looks puzzling. >> What is your default shell? >> If it is not bash, then there might be strange problems like this. What is the output of >> >> echo $SHELL >> >> >> >> On Mon, 3 Sep 2018, 19:48 Nagesh Adluru, wrote: >>> >>> Hi Dima, >>> >>> I am also getting the output letter just like in your case. It is not crashing. So what would you think is the problem? >>> >>> Also thanks for clarifying about screen! >>> >>> Thanks so much. >>> Nagesh >>> >>> On Mon, Sep 3, 2018 at 5:03 AM Dima Pasechnik wrote: On Sun, Sep 2, 2018 at 11:20 PM Nagesh Adluru wrote: > > Hi David, > > Thanks for sharing that insight. I did install the anaconda in between for a different purpose which explains the new problem with libcurl that I did not have before the libpaper issue. Based on your advice I removed anaconda from the path and I did a full make distclean and reinstall and now the libcurl is gone but it still errors after paperconf message (log attached) even though we have libpaper installed (screenshot attached). > Please let me know what should I try next since libcurl seems no longer to be a problem and libpaper is installed! > what is the output of 'paperconf' ? Could you try running paperconf at shell prompt, to see if it outputs anything meaningful, e.g. for me it outputs 'letter'. It looks as if it either crashes, or outputs something R is not happy about... $ paperconf letter > Thank you all so much for the help! > Sincerely, >
Re: [sage-devel] r-3.4.4.p0 configure/install error
Hi Dima and John, I got the libstd++-static installed. I did not use screen this time. I am not sure how to make "check ...static libraries" to yes. The gcc, g++ and gfortran are all version 7.3.1 20180303 (Red Hat 7.3.1-5). I am still getting the error for r. I am attaching the fresh log again just in case. Also I was thinking, the latest version of R available is r.3.5.1 and sage is trying to install r.3.4.4. Would upgrading it to r.3.5.1 resolve this mysterious issue? Thanks so much for your insights and help! Sincerely, Nagesh On Mon, Sep 3, 2018 at 5:49 PM Nagesh Adluru wrote: > 1) I realized recently that libstd++-static is missing. I will try to get > those and also try to make "checkstatic libraries" to yes for gfortran. > 2) I will try without screen just to check Dima's hypothesis. > 3) Thanks for sharing your input about paperconf, John! > > I will report back once I try these. > Thanks so much everyone! > Best, > Nagesh > > On Mon, Sep 3, 2018 at 5:17 PM John H Palmieri > wrote: > >> On my OS X machine, I do not have paperconf, and R builds just fine. I >> wonder if screen is getting in the way somehow. Can you try without using >> it? >> >> (According to the log file, gfortran seems to be there. There is no >> working ObjC++ compiler, but I don't think that should be an issue, right?) >> >> >> >> On Monday, September 3, 2018 at 2:33:22 PM UTC-7, Dima Pasechnik wrote: >>> >>> you do have gfortran installed, right? >>> (usually R is one of the last packages to be built, but perhaps you >>> overlooked some errors) >>> >>> The R install log after paperconf would go as follows: >>> >>> ... >>> checking for lpr... lpr >>> checking for paperconf... /usr/bin/paperconf >>> checking whether we are using the GNU Fortran compiler... yes >>> checking whether gfortran accepts -g... yes >>> checking if libtool supports shared libraries... yes >>> checking whether to build shared libraries... yes >>> checking whether to build static libraries... no >>> ... >>> >>> and so I suspect that it misreports a fortran error... >>> >>> >>> >>> On Mon, Sep 3, 2018 at 11:52 PM Nagesh Adluru >>> wrote: >>> > >>> > It is bash and >>> > the output of echo $SHELL is /bin/bash >>> > >>> > >>> > >>> > On Mon, Sep 3, 2018 at 3:44 PM Dima Pasechnik >>> wrote: >>> >> >>> >> looks puzzling. >>> >> What is your default shell? >>> >> If it is not bash, then there might be strange problems like this. >>> What is the output of >>> >> >>> >> echo $SHELL >>> >> >>> >> >>> >> >>> >> On Mon, 3 Sep 2018, 19:48 Nagesh Adluru, >>> wrote: >>> >>> >>> >>> Hi Dima, >>> >>> >>> >>> I am also getting the output letter just like in your case. It is >>> not crashing. So what would you think is the problem? >>> >>> >>> >>> Also thanks for clarifying about screen! >>> >>> >>> >>> Thanks so much. >>> >>> Nagesh >>> >>> >>> >>> On Mon, Sep 3, 2018 at 5:03 AM Dima Pasechnik >>> wrote: >>> >>> On Sun, Sep 2, 2018 at 11:20 PM Nagesh Adluru >>> wrote: >>> > >>> > Hi David, >>> > >>> > Thanks for sharing that insight. I did install the anaconda in >>> between for a different purpose which explains the new problem with libcurl >>> that I did not have before the libpaper issue. Based on your advice I >>> removed anaconda from the path and I did a full make distclean and >>> reinstall and now the libcurl is gone but it still errors after paperconf >>> message (log attached) even though we have libpaper installed (screenshot >>> attached). >>> > Please let me know what should I try next since libcurl seems no >>> longer to be a problem and libpaper is installed! >>> > >>> what is the output of 'paperconf' ? >>> Could you try running paperconf at shell prompt, to see if it >>> outputs >>> anything meaningful, e.g. for me it >>> outputs 'letter'. It looks as if it either crashes, or outputs >>> something R is not happy about... >>> >>> $ paperconf >>> letter >>> >>> >>> > Thank you all so much for the help! >>> > Sincerely, >>> > Nagesh >>> > >>> > On Sun, Sep 2, 2018 at 10:06 AM David Einstein >>> wrote: >>> >> >>> >> I don't know about centos, but on OSX this situation occurs when >>> anaconda is installed, and the anaconda directories occur earlier in the >>> path than the system directories. Removing anaconda from the path before >>> building sage fixes the problem. >>> >> >>> >> On Sunday, September 2, 2018 at 8:15:33 AM UTC-4, Nagesh Adluru >>> wrote: >>> >>> >>> >>> I had actually thought of that but the sys admin thought we had >>> the devel installed. I will pursue this line with more pressure now that I >>> have your suggestion as well. >>> >>> >>> >>> Thanks again so much for the prompt help! >>> >>> Best, >>> >>> Nagesh >>> >>> >>> >>> On Sun, Sep 2, 2018, 2:12 AM Dima Pasechnik >>> wrote: >>> >>> >>> >>> On Sunday, Septem
Re: [sage-devel] Tools to compute Hilbert Poincaré series
Note that some interest has recently emerged in renewing the Sage's interface to Macaulay2, see - Sage trac ticket 25885 Fixes for outdated Macaulay2 interface https://trac.sagemath.org/ticket/25885 For other Sage tickets related to Macaulay2, see https://trac.sagemath.org/query?order=id&desc=1&summary=~macaulay2 -- 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@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Enabling Merge Requests from GitLab
On Tue, Sep 4, 2018 at 3:02 PM Daniel Krenn wrote: > > On 09/04/2018 02:33 PM, Jeroen Demeyer wrote: > > Let me make one important comment (something that I've said before > > though): a large part of what makes the current workflow work is not so > > much Trac itself but our git server and the "git trac" scripts. > > > > For example, I very much like the fact that we have a single git repo > > where all pull requests appear. Checking out a pull request for > > reviewing is so much easier with Sage than it is with typical GitHub > > projects. If we ever move to GitLab, we really should keep this workflow. > > This should not be a problem (i.e. adapting git-trac to a git-gitlab) as > Gitlab has a convenient API. > > See, for example, > https://docs.gitlab.com/ee/api/merge_requests.html#get-single-mr > which provides all information needed. Here's a real world sample of using the GitLab API from the GitLab<->Trac bot. In particular, linked is the method that closes a merge request if the associated Trac ticket is closed. It's fairly simple: https://github.com/sagemath/sage_trac_plugin/blob/master/sage_trac/gitlab.py#L416 And it would be even simpler if I were using the Python API that exists for GitLab; here I was just lazy about it, and wanted to get more direct experience with the HTTP API directly (since it was only for a few simple cases) before switching over to the higher-level Pythonic API. -- 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@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Enabling Merge Requests from GitLab
Keeping in mind that this is still sort of off-topic, in my mind, from the subject at hand which is allowing merge request submissions from GitLab, which still get turned into Trac tickets... On Tue, Sep 4, 2018 at 2:33 PM Jeroen Demeyer wrote: > > Let me make one important comment (something that I've said before > though): a large part of what makes the current workflow work is not so > much Trac itself but our git server and the "git trac" scripts. Which is in no way unique to Trac. In fact they're part of the custom cobbled-together way we use git + trac. For GitHub there is the very popular "hub" CLI which does the same thing. For GitLab the options are a bit more scattered. This program called "lab" (which mysteriously is hosted on GitHub) purports to wrap "hub" to add GitLab support: https://github.com/zaquestion/lab Admittedly I have not tried it. Even if you love the "git trac" command it would be easy to adapt to GitLab's API. In either case I'm all for having easy to use command-line tools but that is in no way particular to Trac. > For example, I very much like the fact that we have a single git repo > where all pull requests appear. Checking out a pull request for > reviewing is so much easier with Sage than it is with typical GitHub > projects. If we ever move to GitLab, we really should keep this workflow. I don't like it. I think it's a mess; especially since people don't delete their branches after they're merged (I have not been as good about that myself as I would like). But that's also why we set up https://gitlab.com/sagemath/dev/sage , which mirrors all the trac branches, and that anyone granted write access can create branches on, and create merge requests from those branches. I find it odd that you put these two issues side-by-side, since having a good CLI tool also makes it trivial to check out a branch from a remote fork *shrug* -- 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@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Enabling Merge Requests from GitLab
On 09/04/2018 02:33 PM, Jeroen Demeyer wrote: > Let me make one important comment (something that I've said before > though): a large part of what makes the current workflow work is not so > much Trac itself but our git server and the "git trac" scripts. > > For example, I very much like the fact that we have a single git repo > where all pull requests appear. Checking out a pull request for > reviewing is so much easier with Sage than it is with typical GitHub > projects. If we ever move to GitLab, we really should keep this workflow. This should not be a problem (i.e. adapting git-trac to a git-gitlab) as Gitlab has a convenient API. See, for example, https://docs.gitlab.com/ee/api/merge_requests.html#get-single-mr which provides all information needed. Daniel -- 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@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Enabling Merge Requests from GitLab
On Tue, Sep 4, 2018 at 2:33 PM Jeroen Demeyer wrote: > > Let me make one important comment (something that I've said before > though): a large part of what makes the current workflow work is not so > much Trac itself but our git server and the "git trac" scripts. > > For example, I very much like the fact that we have a single git repo > where all pull requests appear. Checking out a pull request for > reviewing is so much easier with Sage than it is with typical GitHub > projects. Why? A GitHub pull request at a repo X is, internally, a branch on the repo X. So you can change the branch on your clone of X, just as you do on a single git repo workflow. See https://help.github.com/articles/checking-out-pull-requests-locally/ (or https://hub.github.com/hub-checkout.1.html - if you want to use their command line tool 'hub') Dima > If we ever move to GitLab, we really should keep this workflow. > > -- > 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@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- 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@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Enabling Merge Requests from GitLab
Let me make one important comment (something that I've said before though): a large part of what makes the current workflow work is not so much Trac itself but our git server and the "git trac" scripts. For example, I very much like the fact that we have a single git repo where all pull requests appear. Checking out a pull request for reviewing is so much easier with Sage than it is with typical GitHub projects. If we ever move to GitLab, we really should keep this workflow. -- 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@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Tools to compute Hilbert Poincaré series
Hi Dima, On 2018-09-04, Dima Pasechnik wrote: > M2 needs a libgc-compatible version of everything, including fflas. That's > probably why > two copies etc. > > > M2 is maintained and developed. What is not maintained is Sagemath's M2 > package. I see. In that case: *IF* someone explains to me how to build and install M2 (currently it fails for me), I might be able to create a new M2 spkg; and *IF* Macaulay2 is able to compute my example easily and much faster than the implementation that I currently do in Sage, then I can consider to make my group cohomology package depend on it. Best regards, Simon -- 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@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Tools to compute Hilbert Poincaré series
On Tue, 4 Sep 2018, 11:57 Simon King, wrote: > Hi Clement, > > On 2018-09-04, Clement Pernet wrote: > > Le 02/09/2018 à 14:13, Simon King a écrit : > >> > /home/king/Projekte/Macaulay2/M2/M2/usr-host/include/fflas-ffpack/fflas/fflas_ftrsm_src.inl:279:27: > error: ‘openblas_set_num_threads’ was not declared in this scope > >> openblas_set_num_threads(__FFLASFFPACK_OPENBLAS_NUM_THREADS); > >> ^ > >> cc1plus: warning: unrecognized command line option > ‘-Wno-mismatched-tags’ > >> ../../include/config.Makefile:226: recipe for target 'interface.o' > failed > >> make[2]: *** [interface.o] Error 1 > >> make[2]: Leaving directory > '/home/king/Projekte/Macaulay2/M2/M2/Macaulay2/d' > >> Makefile:20: recipe for target 'all-in-d' failed > >> make[1]: *** [all-in-d] Error 2 > >> ==> Currently Macaulay2 is no option. > > > > Hi, > > > > Actually, not only givaro but also fflas-ffpack (another dependency of > macaulay2) is in sagemath. > > Your compilation error seem to indicate a mess in the configuration: you > have probably 2 installs of > > fflas-ffpack, one in SageMath, the other one in Macaulay2 of different > versions and this likely > > causes the compilation failure. > M2 needs a libgc-compatible version of everything, including fflas. That's probably why two copies etc. > Maybe use the Sage's provided givaro is a bad idea as it forces you to > also know about Sage's > > fflas-ffpack and I don't know if it is possible to disable Macaulay's > fflas-ffpack when configuring it. > > Problem: How to install givaro? "sudo apt-get install givaro" doesn't > work, and libgivaro-dev is already installed (actually I installed it as > advised by Macaulay2's INSTALL instructions. And when I just did > ./configure --enable-download followed by "make" again, the error bacame > differently: > make: Entering directory '/home/king/Projekte/Macaulay2/M2/M2' > : "checking for strings that look like undefined configure variables > in all *.in files..." > C libraries all > make: C: Command not found > GNUmakefile:194: recipe for target 'all-in-libraries' failed > make: [all-in-libraries] Error 127 (ignored) > > etc. > > But I think at some point in this thread someone has said that Macaulay2 > isn't actually maintained. M2 is maintained and developed. What is not maintained is Sagemath's M2 package. So, I really don't think I shoud make my > group cohomology package depend on it. > > Best regards, > Simon > > -- > 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@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. > -- 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@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Tools to compute Hilbert Poincaré series
Hi Clement, On 2018-09-04, Clement Pernet wrote: > Le 02/09/2018 à 14:13, Simon King a écrit : >> /home/king/Projekte/Macaulay2/M2/M2/usr-host/include/fflas-ffpack/fflas/fflas_ftrsm_src.inl:279:27: >> error: ‘openblas_set_num_threads’ was not declared in this scope >> openblas_set_num_threads(__FFLASFFPACK_OPENBLAS_NUM_THREADS); >> ^ >> cc1plus: warning: unrecognized command line option ‘-Wno-mismatched-tags’ >> ../../include/config.Makefile:226: recipe for target 'interface.o' failed >> make[2]: *** [interface.o] Error 1 >> make[2]: Leaving directory '/home/king/Projekte/Macaulay2/M2/M2/Macaulay2/d' >> Makefile:20: recipe for target 'all-in-d' failed >> make[1]: *** [all-in-d] Error 2 >> ==> Currently Macaulay2 is no option. > > Hi, > > Actually, not only givaro but also fflas-ffpack (another dependency of > macaulay2) is in sagemath. > Your compilation error seem to indicate a mess in the configuration: you have > probably 2 installs of > fflas-ffpack, one in SageMath, the other one in Macaulay2 of different > versions and this likely > causes the compilation failure. > Maybe use the Sage's provided givaro is a bad idea as it forces you to also > know about Sage's > fflas-ffpack and I don't know if it is possible to disable Macaulay's > fflas-ffpack when configuring it. Problem: How to install givaro? "sudo apt-get install givaro" doesn't work, and libgivaro-dev is already installed (actually I installed it as advised by Macaulay2's INSTALL instructions. And when I just did ./configure --enable-download followed by "make" again, the error bacame differently: make: Entering directory '/home/king/Projekte/Macaulay2/M2/M2' : "checking for strings that look like undefined configure variables in all *.in files..." C libraries all make: C: Command not found GNUmakefile:194: recipe for target 'all-in-libraries' failed make: [all-in-libraries] Error 127 (ignored) etc. But I think at some point in this thread someone has said that Macaulay2 isn't actually maintained. So, I really don't think I shoud make my group cohomology package depend on it. Best regards, Simon -- 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@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Tools to compute Hilbert Poincaré series
Le 02/09/2018 à 14:13, Simon King a écrit : 5. Use Macaulay2 Bad: (a) The experimental spkg is broken, it won't install. (b) The installation instructions for Ubuntu on the project pages are rather verbose and require adding obscure repositories. (c) Installation from sources (release-1.12 from github): i. Although I installed all dependencies listed in the INSTALL file, "make" fails because additionally givaro is required. And 'export MAKE="make -j3"' makes Macaulay2 believe that gnu make is not installed. ii. I tried installation in a Sage shell, as givaro is in Sage. However, "make" fails as follows: /home/king/Projekte/Macaulay2/M2/M2/usr-host/include/fflas-ffpack/fflas/fflas_ftrsm_src.inl:279:27: error: ‘openblas_set_num_threads’ was not declared in this scope openblas_set_num_threads(__FFLASFFPACK_OPENBLAS_NUM_THREADS); ^ cc1plus: warning: unrecognized command line option ‘-Wno-mismatched-tags’ ../../include/config.Makefile:226: recipe for target 'interface.o' failed make[2]: *** [interface.o] Error 1 make[2]: Leaving directory '/home/king/Projekte/Macaulay2/M2/M2/Macaulay2/d' Makefile:20: recipe for target 'all-in-d' failed make[1]: *** [all-in-d] Error 2 ==> Currently Macaulay2 is no option. Hi, Actually, not only givaro but also fflas-ffpack (another dependency of macaulay2) is in sagemath. Your compilation error seem to indicate a mess in the configuration: you have probably 2 installs of fflas-ffpack, one in SageMath, the other one in Macaulay2 of different versions and this likely causes the compilation failure. Maybe use the Sage's provided givaro is a bad idea as it forces you to also know about Sage's fflas-ffpack and I don't know if it is possible to disable Macaulay's fflas-ffpack when configuring it. Clément -- 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@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Enabling Merge Requests from GitLab
On Mon, Sep 3, 2018 at 5:04 PM Jeroen Demeyer wrote: > > On 2018-09-03 15:53, Erik Bray wrote: > > P.S. If anyone has additional comments, positive or negative, on > > https://trac.sagemath.org/ticket/25914 they would be most appreciated > > That doesn't seem the right ticket. No, that's the right one. It's the ticket that motivates enabling merge requests in the first place. -- 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@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Tools to compute Hilbert Poincaré series
FWIW: Hannes wrote in the Singular forum that he finds it a bad idea to use 64 bit integers, because it would behave differently on 32bit machines. He also argues that bigint vectors exist in Singular, since there are bigint *matrices* in Singular; right, but the syntax is different and thus it isn't a drop-in replacement. And he wrote that making hilb(id,1) use bigint vectors would imply a complete rewrite of the function, and if I volunteer to implement it; although I'd expect that it is mainly "search-and-replace", I am not so sure if I volunteer. So, at the moment I am trying to implement something in Sage, using sage.rings.polynomial.polydict.ETuple as data structure. I guess the implementation will go to either sage.rings.polynomial.polydict or better to a new module sage.rings.polynomial.hilbert. Best regards, Simon -- 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@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
