Re: [sage-devel] Re: Silent mode for make and quiet mode for configure

2020-07-30 Thread Samuel Lelièvre
Thanks, I opened a ticket: - Have configure run quiet if started by make in silent mode https://trac.sagemath.org/ticket/30258 2020-07-30 22:13 UTC, Matthias Koeppe: > > That's a nice idea, please open a ticket for it > > On Thursday, July 30, 2020 at 10:05:35 AM UTC-7, Samuel Lelievre wrote: >

[sage-devel] Re: Silent mode for make and quiet mode for configure

2020-07-30 Thread Matthias Koeppe
That's a nice idea, please open a ticket for it On Thursday, July 30, 2020 at 10:05:35 AM UTC-7, Samuel Lelievre wrote: > > Dear sage-devel, > > A technical question re building Sage from source. > > Having set `make` to silent mode eg using > > MAKE='make -s V=0' > > one would expect that in

[sage-devel] Silent mode for make and quiet mode for configure

2020-07-30 Thread Samuel Lelievre
Dear sage-devel, A technical question re building Sage from source. Having set `make` to silent mode eg using MAKE='make -s V=0' one would expect that in cases in which `make` or `make distclean` calls `./configure`, it would call it in quiet mode: `./configure -q`. Is there some way to e

[sage-devel] Re: assume() seems to break integrate() in some cases

2020-07-30 Thread kcrisman
On Wednesday, July 29, 2020 at 2:48:58 PM UTC-4, rjf wrote: > > The development of Macsyma, and Maxima, in a manner similar to that of > Sage, > was/is essentially the accumulation of contributions from many hands. > Sometimes pieces added later have unanticipated effects on older > code. So thi

[sage-devel] Re: assume() seems to break integrate() in some cases

2020-07-30 Thread kcrisman
On Thursday, July 30, 2020 at 2:29:57 AM UTC-4, Nils Bruin wrote: > > On Wednesday, July 29, 2020 at 11:03:00 PM UTC-7, Sébastien Labbé wrote: >> >> Would it be hard to implement both: >> >> .integrate(algorithm='maxima_domain_real') >> .integrate(algorithm='maxima_domain_complex') >> >> ? >> > N

Re: [sage-devel] git status keeps saying modified: build/pkgs/cunningham_tables/main.gz

2020-07-30 Thread Dima Pasechnik
On Thu, Jul 30, 2020 at 9:31 AM Sébastien Labbé wrote: > > > > On Thursday, July 30, 2020 at 10:12:10 AM UTC+2, Dima Pasechnik wrote: >> >> On Thu, Jul 30, 2020 at 8:37 AM Sébastien Labbé wrote: >> > >> > Dear sage-devel, >> > >> > When I update my sage version, I never do a fresh clone. I always

Re: [sage-devel] git status keeps saying modified: build/pkgs/cunningham_tables/main.gz

2020-07-30 Thread Sébastien Labbé
On Thursday, July 30, 2020 at 10:12:10 AM UTC+2, Dima Pasechnik wrote: > > On Thu, Jul 30, 2020 at 8:37 AM Sébastien Labbé > wrote: > > > > Dear sage-devel, > > > > When I update my sage version, I never do a fresh clone. I always pull > the most recent develop branch. Everything always wor

Re: [sage-devel] git status keeps saying modified: build/pkgs/cunningham_tables/main.gz

2020-07-30 Thread Dima Pasechnik
On Thu, Jul 30, 2020 at 8:37 AM Sébastien Labbé wrote: > > Dear sage-devel, > > When I update my sage version, I never do a fresh clone. I always pull the > most recent develop branch. Everything always work. > > But now, my git status keeps telling me that > build/pkgs/cunningham_tables/main.gz

[sage-devel] git status keeps saying modified: build/pkgs/cunningham_tables/main.gz

2020-07-30 Thread Sébastien Labbé
Dear sage-devel, When I update my sage version, I never do a fresh clone. I always pull the most recent develop branch. Everything always work. But now, my git status keeps telling me that build/pkgs/cunningham_tables/main.gz is modified and I found no way to get rid of that (git checkout buil