On Friday, July 17, 2020 at 4:05:22 PM UTC-7, Dima Pasechnik wrote:
>
> one can trigger tests on GitHub Actions, which will be testing in such a
> case, too.
> See developer manual on how this is done.
>
>>
>>
I have already run automated portability tests through GH Actions on this
ticket.
What
one can trigger tests on GitHub Actions, which will be testing in such a
case, too.
See developer manual on how this is done.
basically, fork Sage on github and issue a pull request to your own repo.
On Fri, 17 Jul 2020, 23:42 Emmanuel Charpentier, <
emanuel.charpent...@gmail.com> wrote:
> I gav
I gave a positive review to this ticket, using a Sage system ysing the
system's R installation (Debian packaged). This should (must ?) be, by all
means, re-checked on a system using Sage's own R packaging...
Le jeudi 16 juillet 2020 16:44:13 UTC+2, Emmanuel Charpentier a écrit :
>
> Currently, o
Hello everyone,
In regards to the interest in making Sagemath present on the Raspberry Pi
platform it would be helpful in also having the GPIO module available in
Sagemath.
It would be helpful to have Sagemath be able to access electronic circuits
e.g. A/D, D/A converters, motor controllers, sens
oops, sorry, you're hitting a more fundamental problem, your clock is
really, really skew.
I believe the error you get is from a typical autoconf-generated
configure script.
I am actually surprised that Sage's top ./configure script does not
end with this error.
There isn't much we can do here - p
On Friday, July 17, 2020 at 1:25:51 PM UTC-7, Dima Pasechnik wrote:
>
> A standard way to "fix" this for projects like fplll would be to add
> AM_MAINTAINER_MODE macro to configure.ac, regenerate ./configure
> and then run configure with --disable-maintainer-mode
>
>
We could as well delete conf
On July 17, 2020 5:56:38 PM GMT-03:00, Dima Pasechnik wrote:
>On Fri, Jul 17, 2020 at 9:43 PM 'Reimundo Heluani' via sage-devel
> wrote:
>>
>> On Jul 17, Dima Pasechnik wrote:
>> >A standard way to "fix" this for projects like fplll would be to add
>> >AM_MAINTAINER_MODE macro to configure.ac,
On Fri, Jul 17, 2020 at 9:43 PM 'Reimundo Heluani' via sage-devel
wrote:
>
> On Jul 17, Dima Pasechnik wrote:
> >A standard way to "fix" this for projects like fplll would be to add
> >AM_MAINTAINER_MODE macro to configure.ac, regenerate ./configure
> >and then run configure with --disable-maintai
On Jul 17, Dima Pasechnik wrote:
A standard way to "fix" this for projects like fplll would be to add
AM_MAINTAINER_MODE macro to configure.ac, regenerate ./configure
and then run configure with --disable-maintainer-mode
But I'll have to do this for every pkgs that will be installed? that'll tak
On Jul 17, Dima Pasechnik wrote:
Do you build on a network file system?
Do they have a "scratch" partition you can use, which is on a local disk?
What you see has to do with "skew clocks" on the fileserver vs the CPU you use.
Thanks, yes I think my home is mounted from the network. How would a
I found this which is odd at least to me. The date and timezone on the server
is fine:
heluani@tsunami5:~$ date
sex 17 jul 2020 17:31:38 -03
heluani@tsunami5:~$ touch hello.txt
heluani@tsunami5:~$ ls -l hello.txt
-rw-rw-rw- 1 heluani pesq 0 jul 17 14:31 hello.txt
heluani@tsunami5:~$ TZ="utc" ls
A standard way to "fix" this for projects like fplll would be to add
AM_MAINTAINER_MODE macro to configure.ac, regenerate ./configure
and then run configure with --disable-maintainer-mode
On Fri, Jul 17, 2020 at 9:15 PM Dima Pasechnik wrote:
>
> Do you build on a network file system?
> Do they h
Do you build on a network file system?
Do they have a "scratch" partition you can use, which is on a local disk?
What you see has to do with "skew clocks" on the fileserver vs the CPU you
use.
On Fri, 17 Jul 2020, 21:00 'Reimundo Heluani' via sage-devel, <
sage-devel@googlegroups.com> wrote:
>
13 matches
Mail list logo
