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
to GP prompt
You're right, there's a permission issue:
ls -l /usr/share/pari/seadata/sea211
-rw-r--r-- 1 root root 194468 Sep 15 12:01 /usr/share/pari/seadata/sea211
Thanks.
On 9/16/20 2:45 PM, Dima Pasechnik wrote:
On Wed, Sep 16, 2020 at 1:33 PM Nicolo' Piazzalunga
wrote:
It was on a fresh
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
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:
.com.
From 79e7971a1477705a8f1828a0135dd8eea4c4c844 Mon Sep 17 00:00:00 2001
From: Nicolo' Piazzalunga
Date: Tue, 8 Sep 2020 17:16:31 +0200
Subject: [PATCH] pari-additional packages
---
build/pkgs/pari/distros/void.txt | 4
build/pkgs/pari_elldata/distros/void.txt | 1 +
build/pkgs/pari_galda
I have a slight confusion: for pari, does sage need the seadata package,
or is the -small version enough?
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
We are now able to build sage on void linux by using ./bootstrap,
./configure and make; everything is installed in some local folder,
since make install is a no-op.
Trying to package it, using as many system packages as possible, and
taking advantage of its build and configure features,
is
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
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
:00 2001
From: Nicolo' Piazzalunga
Date: Wed, 19 Aug 2020 17:17:07 +0200
Subject: [PATCH] added two
---
build/pkgs/void-bootstrap.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/build/pkgs/void-bootstrap.txt b/build/pkgs/void-bootstrap.txt
index b8a4585cf1..3b19fa5069 100644
--- a/bu
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
b visit
https://groups.google.com/d/msgid/sage-devel/f5098ce2-574f-2144-0401-05e37e0eb37d%40gmail.com.
>From 9a4ca026b2a145bc8dd29fe761925b9f17ba6f72 Mon Sep 17 00:00:00 2001
From: Nicolo' Piazzalunga
Date: Tue, 18 Aug 2020 16:38:29 +0200
Subject: [PATCH] added r and edited isl
---
build/pkgs
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 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-
up.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/cb8f9305-9fa5-18b4-12f6-7ab80e61e98e%40gmail.com.
>From 27fa52ae37a8b5168ed18a45
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
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
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
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
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
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
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
ppl python3 r rw symmetrica tachyon
On 7/1/20 3:45 PM, Michael Orlitzky wrote:
> 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
$3.4.4"
Package libR was not found in the pkg-config search path.
Perhaps you should add the directory containing `libR.pc'
to the PKG_CONFIG_PATH environment variable
On Fri, Jul 3, 2020 at 10:10 AM Nicolo' Piazzalunga
wrote:
Sure,
tar xvf sage-9.1.tar.gz
cd sage-9.1
./configure
gives this.
: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 only after
that's done
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
26 matches
Mail list logo
