If your Sage build is incomplete, some packages have been built, say,
pari, and then you decide to replace pari
with a system package then you need to uninstall it.
In your config.log there is
configure:38410: result: pari-2.11.4.p0:
already installed as an SPKG
e.g. for pari you'd need to run
... or should I uninstall systemwide giac?
Tobias Weiss schrieb am Samstag, 28. November 2020 um 22:00:05 UTC+1:
> In my opinion it is again a conflict between systemwide packages and
> tarball. As I said ./configure does not recognize system giac, but maybe
> make does. Tomorrow I will
In my opinion it is again a conflict between systemwide packages and
tarball. As I said ./configure does not recognize system giac, but maybe
make does. Tomorrow I will configure like this and will make:
./configure --with-system-giac=no
What do you think? Is it senseful?
Tobias
Tobias
And proceeding started like this - it let giac untouched:
*~/bin/sage-9.2> make giac && make make build/make/Makefile --stop make[1]:
Verzeichnis „/home/tobias/bin/sage-9.2“ wird betreten make[1]:
„build/make/Makefile“ ist bereits aktuell. make[1]: Verzeichnis
On Sat, 28 Nov 2020, 19:41 Tobias Weiss, wrote:
> I understand: I start a new compilation with "make giac && make". It
> starts with readline and does pari now very early.
>
no, not a new one.
Normally one can (and should) proceed at the point it stopped.
> Tobias Weiss schrieb am Samstag,
... when I configured like this, sagelib was compliled without errors. See
thread "Building of sage 9.2 stopped because pynac doesn't see libflint" I
did before.
*./configure --with-system-arb=no --with-system-boost=no
--with-system-brial=no --with-system-cddlib=no
On system I had installed giac for all the builds I have done:
giac 1.5.0.85-1.1
giac-devel 1.5.0.85-1.1
libgiac0 1.5.0.85-1.1
But ./configure didn't notice. Should I retry with uninstall giac?
Tobias
Tobias Weiss schrieb am Samstag, 28. November 2020 um 20:52:51 UTC+1:
> Compiling with
Compiling with "make giac && make" stopped with giac. I give you the log.
*[giac-1.5.0.87p2.p1] checking for lapack... no [giac-1.5.0.87p2.p1]
configure: error: Package requirements (lapack) were not met:
[giac-1.5.0.87p2.p1] [giac-1.5.0.87p2.p1]
I understand: I start a new compilation with "make giac && make". It starts
with readline and does pari now very early.
Tobias Weiss schrieb am Samstag, 28. November 2020 um 20:31:13 UTC+1:
> In what directory I should do "make giac && make" ?
>
> Tobias Weiss schrieb am Samstag, 28. November
In what directory I should do "make giac && make" ?
Tobias Weiss schrieb am Samstag, 28. November 2020 um 20:29:11 UTC+1:
> Here the top-level config.log. Giac was compiled without problems bevor
> sagelib. I give you the install logs of both. Installing the static-devel
> of glibc didn't
The actual error is likely further up. This problem could just be the
missing dependency of sagelib on giac, already fixed
in https://trac.sagemath.org/ticket/30858
Try compiling the latest development version,
or do "make giac && make" to work around the problem
On Saturday, November 28, 2020
Those who want to help with this problem may
find https://trac.sagemath.org/ticket/30619 useful -- builds on this system
can be reproduced using "tox -e docker-opensuse-tumbleweed-standard"
On Saturday, November 28, 2020 at 10:23:52 AM UTC-8 Dima Pasechnik wrote:
> please post the top-level
please post the top-level config.log
On Sat, 28 Nov 2020, 17:32 Tobias Weiss, wrote:
> Because the last g++ command is something with stl vector: Do I need the
> glibc-static-devel? I only have glibc-devel installed.
>
> Tobias
>
>
> Tobias Weiss schrieb am Samstag, 28. November 2020 um
Because the last g++ command is something with stl vector: Do I need the
glibc-static-devel? I only have glibc-devel installed.
Tobias
Tobias Weiss schrieb am Samstag, 28. November 2020 um 16:25:24 UTC+1:
> Hello Everybody,
>
> now the second post to the problem. I try to make sage 9.2 on
Hello Everybody,
now the second post to the problem. I try to make sage 9.2 on Opensuse
Tumbleweed. The compilation stopped with last step of sagelib. If I don't
take system packages, the error don't occurs.
(see thread https://groups.google.com/g/sage-support/c/AJRosgRDrsE)
Pari was take from
OK, now taking system packages again, the compilation stopped with sagelib
again. I'll make a new thread, because its another problem, I think ...
Tobias
Tobias Weiss schrieb am Samstag, 28. November 2020 um 13:16:22 UTC+1:
> Is it possible to create a rpm file after build? If I install sage
Is it possible to create a rpm file after build? If I install sage with
rpm, the system knows about all dependencies and warns me if I'm going to
hurt them.
Tobias
dim...@gmail.com schrieb am Freitag, 27. November 2020 um 22:53:06 UTC+1:
> On Fri, Nov 27, 2020 at 9:36 PM Tobias Weiss wrote:
17 matches
Mail list logo
