Problem seems now solved.
I updated ticket #30539, where I included extra pari spkgs.
Thanks.
--
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
Same from gp prompt:
? poldegree(ellmodulareqn(211)[1])
*** at top-level: poldegree(ellmodulareqn(211)[1])
*** ^--
*** ellmodulareqn: error opening seadata file:
`/usr/share/pari/seadata/sea211'.
*** Break loop: type 'break' to go back
On Wed, Sep 16, 2020 at 1:33 PM Nicolo' Piazzalunga
wrote:
>
> It was on a fresh install, see the attached config.log
>
does
poldegree(ellmodulareqn(211)[1])
work at the gp prompt, interactively (with the same user id as used
for running ./configure)
(more precisely, your gp is found in /bin/,
If you are trying this on an existing install, did you run
make pari-clean
before trying ./configure ?
Please send the top-level config.log
On Wed, Sep 16, 2020 at 8:48 AM Nicolo' Piazzalunga
wrote:
>
> Thanks. I get:
>
> ? default(datadir)
> %1 = "/usr/share/pari"
>
> so it seems it is
Thanks. I get:
? default(datadir)
%1 = "/usr/share/pari"
so it seems it is correctly configured, but still not detected..
On 9/15/20 6:59 PM, Dima Pasechnik wrote:
On Tue, Sep 15, 2020 at 2:11 PM Nicolo' Piazzalunga
mailto:nicolopiazzalu...@gmail.com>> wrote:
I did it.
On
On Tue, Sep 15, 2020 at 2:11 PM Nicolo' Piazzalunga <
nicolopiazzalu...@gmail.com> wrote:
> I did it.
>
> On 9/8/20 5:39 PM, Dima Pasechnik wrote:
> > sure - can you do this yourself?
>
> It seems sage is still unable to detect my pari-seadata package, even
> though the file
I did it.
On 9/8/20 5:39 PM, Dima Pasechnik wrote:
sure - can you do this yourself?
It seems sage is still unable to detect my pari-seadata package, even
though the file /usr/share/pari/seadata/sea211 is present on my system.
Do you know what the problem could be?
configure:17484:
On Tue, Sep 8, 2020 at 4:32 PM Nicolo' Piazzalunga
wrote:
>
> Would it be possible to create a new trac ticket with more void spkg's?
sure - can you do this yourself?
> I attach a patch for pari subpackages (waiting to be merged in void).
> Leaving it open for a while will simplify adding spkg's
Would it be possible to create a new trac ticket with more void spkg's?
I attach a patch for pari subpackages (waiting to be merged in void).
Leaving it open for a while will simplify adding spkg's and building.
Thanks.
--
You received this message because you are subscribed to the Google
On 8/21/20 7:19 PM, Samuel Lelievre wrote:
>
> The ticket to upgrade Sage-the-distribution to Python 3.8
> just got positive review:
>
>https://trac.sagemath.org/ticket/27754
>
Thanks. I also give it a positive review, hopefully it'll be merged
soon. Now on my Void machine sage builds in
2020-08-21 12:40:44 UTC, Nicolo':
>
> Is there a ticket already to use python3.8 from system?
The ticket to upgrade Sage-the-distribution to Python 3.8
just got positive review:
https://trac.sagemath.org/ticket/27754
By clicking on the link in the "Branch" field one can see
that it changes
Finally sage builds successfully on void linux :)
I will add spkg files for pari-seadata etc as soon as the packages are
approved, this way it does not have to build pari and giac.
Is there a ticket already to use python3.8 from system?
Should I be worried that it fails some doctest?
sage -t
Thanks. I've pushed this to https://trac.sagemath.org/ticket/30382
On Wednesday, August 19, 2020 at 8:20:38 AM UTC-7, Nicolo' wrote:
>
> > these missing pari/gp parts are just data, easy to packageGood, working
> on that.
> In the meantime, it is useful to add a few pkgs to bootstrap
On Wed, Aug 19, 2020 at 4:20 PM Nicolo' Piazzalunga
wrote:
>
> > these missing pari/gp parts are just data, easy to packageGood, working on
> > that.
> In the meantime, it is useful to add a few pkgs to bootstrap (attached).
Please open a trac ticket on this, and, ideally, create a branch with
these missing pari/gp parts are just data, easy to packageGood, working on that.
In the meantime, it is useful to add a few pkgs to bootstrap (attached).
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop
On Wed, Aug 19, 2020 at 9:47 AM Nicolo' Piazzalunga
wrote:
>
> On 8/18/20 5:03 PM, Matthias Koeppe wrote:
> > Try again after "./bootstrap" (this needs autotools installed)
>
> Thanks, now it checks, but since pari misses some parts, it doesn't
> detect giac either.
these missing pari/gp parts
On 8/18/20 5:03 PM, Matthias Koeppe wrote:
> Try again after "./bootstrap" (this needs autotools installed)
Thanks, now it checks, but since pari misses some parts, it doesn't
detect giac either.
## - ##
## Checking whether SageMath should
Try again after "./bootstrap" (this needs autotools installed)
On Tuesday, August 18, 2020 at 7:41:41 AM UTC-7, Nicolo' wrote:
>
> Thanks, I figured out almost all my issues.
> Except, only mention of giac in config.log is
>
> giac-1.5.0.87: does not support check for system package
>
>
Thanks, I figured out almost all my issues.
Except, only mention of giac in config.log is
giac-1.5.0.87: does not support check for system package
Shouldn't it be able to check it by now?
I attach a patch for R and isl15-devel.
On 8/18/20 3:25 PM, Matthias Koeppe wrote:
config.log has more
config.log has more information on why packages are rejected
On Tuesday, August 18, 2020 at 1:37:09 AM UTC-7, Nicolo' wrote:
>
> After importing
> u/mkoeppe/spkg_configure_m4_for_giac
> u/mkoeppe/more_voidlinux_txt
> and d43730c (should this appear in beta9?),
> I still get
>
> the following
After importing
u/mkoeppe/spkg_configure_m4_for_giac
u/mkoeppe/more_voidlinux_txt
and d43730c (should this appear in beta9?),
I still get
the following SPKGs did not find equivalent system packages: arb brial
cddlib cliquer coxeter3 eclib fflas_ffpack flint flintqs fplll gf2x gfan
givaro gp2c
On Monday, August 17, 2020 at 4:34:51 AM UTC-7, Nicolo' wrote:
>
> I have added pari, which I either previously overlooked or has been
> recently added.
>
Thanks. I have put it on https://trac.sagemath.org/ticket/30382
>
> Void people should be taking care of renaming docker images.
>
On 8/17/20 1:34 PM, Nicolo' Piazzalunga wrote:
Giac is already at 1.5.0.87, so perhaps try the new spkg-configure.m4?
Indeed if I try to build /sage-9.2.beta8, it only fails with
giac-1.5.0.63-p0
--
You received this message because you are subscribed to the Google Groups
"sage-devel"
I have added pari, which I either previously overlooked or has been
recently added.
Void people should be taking care of renaming docker images.
Giac is already at 1.5.0.87, so perhaps try the new spkg-configure.m4?
On 7/29/20 8:06 PM, Matthias Koeppe wrote:
R builds successfully.
On
R builds successfully.
On Wednesday, July 29, 2020 at 9:46:48 AM UTC-7, Nicolo' wrote:
>
> On 7/24/20 7:53 PM, Matthias Koeppe wrote:
> > On Wednesday, July 22, 2020 at 10:21:31 AM UTC-7, Matthias Koeppe wrote:
> >
> > I'll run another round of tests with "tox -e
> >
On 7/24/20 7:53 PM, Matthias Koeppe wrote:
On Wednesday, July 22, 2020 at 10:21:31 AM UTC-7, Matthias Koeppe wrote:
I'll run another round of tests with "tox -e
docker-voidlinux-standard" now.
It reproduces the build failure of giac-1.5.0.63-p0 that you reported.
Note that although
On Wednesday, July 22, 2020 at 10:21:31 AM UTC-7, Matthias Koeppe wrote:
>
> I'll run another round of tests with "tox -e docker-voidlinux-standard"
> now.
>
It reproduces the build failure of giac-1.5.0.63-p0 that you reported.
Note that although you added the giac system package information,
On Thursday, July 23, 2020 at 11:18:52 PM UTC-7, Nicolo' wrote:
>
> > By the way, I noticed that there is no "latest" tag on the Docker image.
> > Perhaps the voidlinux people could add this.
>
> Note that Void Linux is a rolling release.
>
Exactly -- right now I am forced to hardcode
By the way, I noticed that there is no "latest" tag on the Docker image.
Perhaps the voidlinux people could add this.
Note that Void Linux is a rolling release.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and
Thank you. I have added it to the branch.
It's better to post these files as an attachment - as inline text it gets
mangled by Google Groups.
Also, see
https://doc.sagemath.org/html/en/developer/git_setup.html#your-name-and-email
I'll run another round of tests with "tox -e
Sorry, that was likely a typo from me.
Does it work now? is the format ok?
From bfd28b43c42cf2f24427f9ac0fa0c4bcd8dc475e Mon Sep 17 00:00:00 2001
From: nicolo
Date: Wed, 22 Jul 2020 15:46:41 +0200
Subject: [PATCH] remove glib2 (typo?)
---
build/pkgs/freetype/distros/void.txt | 1 -
1 file
I am getting the following error:
Aborting!
Package `which' already installed.
Unable to locate 'glib2' in repository pool.
The command '/bin/sh -c xbps-install -Su && xbps-install --yes binutils
make m4 perl python3 tar bc gcc which gettext autoconf automake libtool
pkg-config
Thank you. I have added it to the branch.
By the way, I noticed that there is no "latest" tag on the Docker image.
Perhaps the voidlinux people could add this.
Also, for sending patches here in the group, it's best to use "git commit"
followed by "git format-patch".
On Saturday, July 11,
With this, we should get close to the list of explicitly installed
packages on my machine (attached).
On 7/10/20 6:18 PM, Matthias Koeppe wrote:
Thanks. More packages, please
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe
On Friday, July 10, 2020 at 6:55:06 AM UTC-7, Nicolo' wrote:
>
>
> diff --git a/build/pkgs/giac/distros/void.txt
> b/build/pkgs/giac/distros/void.txt
> new file mode 100644
> index 00..daf8fd8679
> --- /dev/null
> +++ b/build/pkgs/giac/distros/void.txt
> @@ -0,0 +1,2 @@
>
the ecl 20 ticket has been positively reviewed. there is no need to spend
time fighting problems caused by the outdated ecl 16.
On Fri, 10 Jul 2020, 14:55 Nicolo' Piazzalunga,
wrote:
> Let us include giac-devel (1.5.0.87):
>
> diff --git a/build/pkgs/giac/distros/void.txt
>
Let us include giac-devel (1.5.0.87):
diff --git a/build/pkgs/giac/distros/void.txt
b/build/pkgs/giac/distros/void.txt
new file mode 100644
index 00..daf8fd8679
--- /dev/null
+++ b/build/pkgs/giac/distros/void.txt
@@ -0,0 +1,2 @@
+giac-devel
+libgiac
It seems ecl (16.1.3) needs to be
Also the "giac" build error is confirmed.
On the other hand "r" and "suitesparse" build successfully.
To reproduce the build errors that you reported, information about
equivalent distribution packages needs to be added to
build/pkgs/*/distros/void.txt
On Wednesday, July 8, 2020 at 8:10:37
I can already confirm a build error in the ecl package.
You may want to try with ticket https://trac.sagemath.org/ticket/22191 ,
which makes a major update to ECL.
On Wednesday, July 8, 2020 at 6:56:02 AM UTC-7, Matthias Koeppe wrote:
>
> Thanks. I have added gettext-devel to
Thanks. I have added gettext-devel to build/pkgs/void-bootstrap.txt on the
ticket.
"tox -e docker-voidlinux-standard" is now beginning to build Sage. I'll let
you know if it reproduces the errors that you reported.
On Wednesday, July 8, 2020 at 5:39:28 AM UTC-7, Nicolo' wrote:
>
> Does adding
Does adding
libltdl-devel python3-pkgconfig gettext-devel
help?
On 7/7/20 9:18 PM, Matthias Koeppe wrote:
Thanks. I have put your changes on the branch of
https://trac.sagemath.org/ticket/30044 and did some additional changes.
You can now test using:
tox -e docker-voidlinux-standard
Thanks. I have put your changes on the branch of
https://trac.sagemath.org/ticket/30044 and did some additional changes.
You can now test using:
tox -e docker-voidlinux-standard
Currently, it fails as follows:
src/doc/bootstrap:85: installing src/doc/en/reference/repl/options.txt
gettext and
I tried to edit relevant files, see diff.log attached.
Please check docker-specific files, as I'm not familiar with it.
(The relevant image in docker-hub is /voidlinux/masterdir-x86_64-musl)
I have not yet dealt with equivalent distribution packages, if it's ok I
will do it once we have no build
On Fri, Jul 3, 2020 at 2:34 PM Nicolo' Piazzalunga
wrote:
>
> Sure, just let me know what to do.
> In the meantime, let me note that I can build both R-3.6.2 and R-4.0.2
> standalone with ./configure --with-x=no
you can go to the directory where R was being built by Sage
(where exactly you can
Edit build/bin/sage-guess-package-system,
build/bin/sage-print-system-package-command, build/bin/write-dockerfile.sh,
tox.ini, and add voidlinux.txt files in build/pkgs/
similar to
https://git.sagemath.org/sage.git/commit?id=eecd68a1a3cd6046a6ae0d4b5eb57895ee34a1ba
More info:
Sure, just let me know what to do.
In the meantime, let me note that I can build both R-3.6.2 and R-4.0.2
standalone with ./configure --with-x=no
On 7/3/20 3:30 PM, Matthias Koeppe wrote:
We will need your help to replicate a voidlinux system for testing – see
We will need your help to replicate a voidlinux system for testing – see
https://trac.sagemath.org/ticket/30044
On Thursday, July 2, 2020 at 11:08:17 AM UTC-7, Nicolo' wrote:
>
> I can build R-4.0.2 as standalone, why does it fail in Sage?
> As for ecl, perhaps wait until we can use system one?
On Fri, 3 Jul 2020, 13:33 Nicolo' Piazzalunga,
wrote:
> Let me clarify: my problem is that Sage still fails to build (r and ecl
> give errors).
> As for ecl, I think I understand the problem (a patch is needed for
> musl), but could ecl trigger failure of r, which I can however build as
> a
Let me clarify: my problem is that Sage still fails to build (r and ecl
give errors).
As for ecl, I think I understand the problem (a patch is needed for
musl), but could ecl trigger failure of r, which I can however build as
a standalone?
At this stage, I have no issues building stuff that
Your gmp installation is incomplete, missing C++ support,
therefore all the packages that depend on gmp are installed,and not
taken from the system.
And there are dozens such packages, eg mpfr,ntl, arb, flint, pari, eclib...
from your config.log:
configure:10030: checking gmp.h usability
On Thu, Jul 2, 2020 at 7:08 PM Nicolo' Piazzalunga
wrote:
>
> I can build R-4.0.2 as standalone, why does it fail in Sage?
> As for ecl, perhaps wait until we can use system one?
> At a lower priority, config is still not seeing python3, together with
>
> arb cddlib cliquer eclib ecm fflas_ffpack
I can build R-4.0.2 as standalone, why does it fail in Sage?
As for ecl, perhaps wait until we can use system one?
At a lower priority, config is still not seeing python3, together with
arb cddlib cliquer eclib ecm fflas_ffpack flint flintqs fplll gf2x gfan
givaro glpk gp2c iml isl lcalc
On 2020-07-01 09:23, Nicolo' Piazzalunga wrote:
> Thanks.
> I'm puzzled by 'does not support check for system package'/'no suitable
> system package' in config.log
We haven't written the script to detect a system copy of ECL yet. We're
in the middle of upgrading to a new major version of it, and
On Wed, Jul 1, 2020 at 2:23 PM Nicolo' Piazzalunga
wrote:
>
> Thanks.
> I'm puzzled by 'does not support check for system package'/'no suitable
> system package' in config.log
> E.g. why is it not finding boost, isl, and why is it building ecl (just
> to list a few), all of which are installed as
Thanks.
I'm puzzled by 'does not support check for system package'/'no suitable
system package' in config.log
E.g. why is it not finding boost, isl, and why is it building ecl (just
to list a few), all of which are installed as system packages?
On 7/1/20 3:15 PM, Michael Orlitzky wrote:
On
On 2020-07-01 08:36, Dima Pasechnik wrote:
>
> In building giac, you get even more strange error, a missing gammaf function.
> (something to do with musl?)
Giac upstream probably needs to
#define _GNU_SOURCE
to get the gammaf() function with musl, since it's not standardized.
--
You
Something is very unusual in your setup; e,g. in building R you get
Error in iconv(x, "UTF-8", outputEncoding, sub = "byte", mark = FALSE) :
unsupported conversion from 'UTF-8' to 'ASCII//TRANSLIT'
In building giac, you get even more strange error, a missing gammaf function.
(something to do
57 matches
Mail list logo
