> On 9 Jun., 13:43, François Bissey <f.r.bis...@massey.ac.nz> wrote:
> > > It does take a long time to build compared to most other packages,
> > > which is probably due to the fact the package is large and so has a
> > > lot of source code.
> >
> > Well I am trying that now. Running the test against a lighter version
> > of singular without what looks like extra baggage.
> > It will have some impact on the build time but probably not as much
> > as you would like. On my computer:
> > before: merge time: 22 minutes and 36 seconds.
> > after : merge time: 18 minutes and 52 seconds.
>
> Nice. I wonder if that "extra baggage" is used/required by the
> Singular interpreter (sage -singular).
>
>
> The new Singular spkg at #9160 has now been merged into the upcoming
> Sage 4.4.4.alpha1.
>
> It fixes the flex issue and some other things, but there's much left
> to do on the package in general (most probably including upgrading to
> a newer upstream release).
>
> We will see what Sage Days 23.5 bring... (see William's post above).
>
I haven't tested your new spkg but I ran
sage -t -long devel/sage/sage/lib/singular/
as you did in your ticket after removing everything that happens
after installing libsingular. My notes in my ebuild are saying:
---------------------------------------------------------------------------------------------
The following is needed to get libfac.a libcf.a? libcfmem.a?
libsingcf_g.a? libsingfac.a? (the last 2 have some defects)
We should check that all these are really needed.
Then if needed check if we could build a specific target rather than
reconfiguring.
-------------------------------------------------------------------------------------------
after removing those:
sage -t -long devel/sage/sage/libs/singular/
sage -t -long "devel/sage/sage/libs/singular/function_factory.py"
[15.9 s]
sage -t -long "devel/sage/sage/libs/singular/singular.pyx"
[19.2 s]
sage -t -long "devel/sage/sage/libs/singular/option.pyx"
[17.1 s]
sage -t -long "devel/sage/sage/libs/singular/polynomial.pyx"
[16.5 s]
sage -t -long "devel/sage/sage/libs/singular/groebner_strategy.pyx"
[17.5 s]
sage -t -long "devel/sage/sage/libs/singular/singular.pxi"
[0.3 s]
sage -t -long "devel/sage/sage/libs/singular/__init__.py"
[0.3 s]
sage -t -long "devel/sage/sage/libs/singular/ring.pyx"
[21.9 s]
sage -t -long "devel/sage/sage/libs/singular/function.pyx"
[24.7 s]
sage -t -long "devel/sage/sage/libs/singular/singular-cdefs.pxi"
[19.8 s]
----------------------------------------------------------------------
All tests passed!
Total time for all tests: 153.3 seconds
I also tested
sage -t -long devel/sage/sage/interfaces/singular.py
sage -t -long "devel/sage/sage/interfaces/singular.py"
[27.8 s]
----------------------------------------------------------------------
All tests passed!
Total time for all tests: 27.8 seconds
So I think it could removed. It may have used at some point in time
but not any more.
Francois
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
