polymake build failure (SageMath 8.9.beta8)

[videlec]

[polymake-3.4] ninja -C build/Opt install
[polymake-3.4] ninja: Entering directory `build/Opt'
[polymake-3.4] [1/8] GENERATE /opt/sage/local/var/tmp/sage/build/polymake-3.4/src/build/applib/fake.c
[polymake-3.4] [2/8] COMPILE /opt/sage/local/var/tmp/sage/build/polymake-3.4/src/build/Opt/lib/callable/stub.o
[polymake-3.4] [3/8] LD /opt/sage/local/var/tmp/sage/build/polymake-3.4/src/build/Opt/lib/callable/libpolymake-apps-rt.so.3.4
[polymake-3.4] [4/8] ln -sf `basename /opt/sage/local/var/tmp/sage/build/polymake-3.4/src/build/Opt/lib/callable/libpolymake-apps-rt.so.3.4` /opt/sage/local/var/tmp/sage/build/polymake-3.4/src/build/Opt/lib/callable/libpolymake-apps-rt.so
[polymake-3.4] [5/8] COMPILE /opt/sage/local/var/tmp/sage/build/polymake-3.4/src/build/Opt/lib/callable/fake.o
[polymake-3.4] [6/8] LD /opt/sage/local/var/tmp/sage/build/polymake-3.4/src/build/Opt/lib/callable/libpolymake-apps.so.3.4
[polymake-3.4] [7/8] ln -sf `basename /opt/sage/local/var/tmp/sage/build/polymake-3.4/src/build/Opt/lib/callable/libpolymake-apps.so.3.4` /opt/sage/local/var/tmp/sage/build/polymake-3.4/src/build/Opt/lib/callable/libpolymake-apps.so
[polymake-3.4] [8/8] INSTALL core system in mode Opt at /opt/sage/local/share/polymake
[polymake-3.4] make[2]: Leaving directory '/opt/sage/local/var/tmp/sage/build/polymake-3.4/src'
[polymake-3.4] 
[polymake-3.4] real	57m8.717s
[polymake-3.4] user	218m56.992s
[polymake-3.4] sys	6m3.984s
[polymake-3.4] Copying package files from temporary location /opt/sage/local/var/tmp/sage/build/polymake-3.4/inst to /opt/sage/local
[polymake-3.4] Running post-install script for polymake-3.4.
[polymake-3.4] polymake:  WARNING: Recompiling in /home/vincent/.polymake/wrappers.0/build/Opt, please be patient...
[polymake-3.4] Compilation failed; see the error log below
[polymake-3.4] 
[polymake-3.4] ninja: Entering directory `/home/vincent/.polymake/wrappers.0/build/Opt'
[polymake-3.4] ninja: fatal: chdir to '/home/vincent/.polymake/wrappers.0/build/Opt' - No such file or directory
[polymake-3.4] ********************************************************************************************************************************************************************************************************************
[polymake-3.4] Error calling 'polymake --reconfigure'
[polymake-3.4] ********************************************************************************************************************************************************************************************************************

CC: @mkoeppe

Component: packages: experimental

Reviewer: Vincent Delecroix

Issue created by migration from https://trac.sagemath.org/ticket/28423

[videlec]

Attachment: polymake-3.4.log

[mkoeppe]

comment:1

Haven't seen this before. Do you have something strange in ~/.polymake?

[videlec]

comment:2

What do you mean by strange?

$ ls ~/.polymake/
customize.pl  history  prefer.pl  wrappers.0  wrappers.1  wrappers.2  wrappers.3

[videlec]

comment:3

Though, after mv .polymake .TMPpolymake compilation went fine.

[videlec]

comment:4

My ~/.polymake folder came from archlinux which ships polymake version 3.5. Might be the source of the trouble.

[mkoeppe]

comment:5

Perhaps some permissions were set wrong in that folder?

[videlec]

comment:6

I am the owner of the files in ~/.polymake/. I did not add manually anything special. And polymake from the system is working fine.

The only reason I can imagine is that polymake 3.5 (from the system) did install some stuff in ~/.polymake/ that perturbed the build of polymake 3.4.

• Is it worth a report to polymake dev?
• Should we have a spkg-configure.m4 to avoid building polymake if already present on the system?
• Should we have some kind of warning when ./polymake is already populated?

[mkoeppe]

comment:7

Replying to @videlec:

• Is it worth a report to polymake dev?

Yes, please do report upstream.

• Should we have a spkg-configure.m4 to avoid building polymake if already present on the system?

Yes, after we upgrade to 3.5. The interface using jupymake requires a threadsafety patch to polymake 3.4; 3.5 has a solution

• Should we have some kind of warning when ./polymake is already populated?

No, I don't think so, let's just switch to 3.5 soon.

[embray]

comment:8

Ticket retargeted after milestone closed

[mkoeppe]

comment:9

I think this can be closed

[kcrisman]

comment:10

Because a newer polymake is included now?

[mkoeppe]

comment:11

This build failure was a user configuration error

[kcrisman]

comment:12

Got it, so Vincent can just confirm to positive review in that case - sorry to ask, it just wasn't clear.

[videlec]

Reviewer: Vincent Delecroix