Opened 2 years ago

Closed 17 months ago

#28423 closed defect (invalid)

polymake build failure (SageMath 8.9.beta8)

Reported by: vdelecroix Owned by:
Priority: major Milestone: sage-duplicate/invalid/wontfix
Component: packages: experimental Keywords:
Cc: mkoeppe Merged in:
Authors: Reviewers: Vincent Delecroix
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description

[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] ********************************************************************************************************************************************************************************************************************

Attachments (1)

polymake-3.4.log (507.0 KB) - added by vdelecroix 2 years ago.

Download all attachments as: .zip

Change History (15)

Changed 2 years ago by vdelecroix

comment:1 Changed 2 years ago by mkoeppe

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

comment:2 Changed 2 years ago by vdelecroix

What do you mean by strange?

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

comment:3 Changed 2 years ago by vdelecroix

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

comment:4 Changed 2 years ago by vdelecroix

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

comment:5 Changed 2 years ago by mkoeppe

Perhaps some permissions were set wrong in that folder?

comment:6 follow-up: Changed 2 years ago by vdelecroix

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?

comment:7 in reply to: ↑ 6 Changed 2 years ago by mkoeppe

Replying to vdelecroix:

  • 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.

comment:8 Changed 21 months ago by embray

  • Milestone changed from sage-8.9 to sage-9.1

Ticket retargeted after milestone closed

comment:9 Changed 17 months ago by mkoeppe

  • Milestone changed from sage-9.1 to sage-duplicate/invalid/wontfix
  • Status changed from new to needs_review

I think this can be closed

comment:10 Changed 17 months ago by kcrisman

Because a newer polymake is included now?

comment:11 Changed 17 months ago by mkoeppe

This build failure was a user configuration error

comment:12 Changed 17 months ago by kcrisman

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

comment:13 Changed 17 months ago by vdelecroix

  • Reviewers set to Vincent Delecroix
  • Status changed from needs_review to positive_review

comment:14 Changed 17 months ago by chapoton

  • Resolution set to invalid
  • Status changed from positive_review to closed
Note: See TracTickets for help on using tickets.