Opened 3 months ago

Last modified 3 months ago

#69287 assigned defect

polymake @4.11: bundled extension libnormaliz ... failed

Reported by: murrayE Owned by: catap (Kirill A. Korinsky)
Priority: Normal Milestone:
Component: ports Version: 2.9.1
Keywords: sonoma arm64 Cc:
Port: polymake

Description

From main.log:

:configure bundled extension libnormaliz ... failed
:info:configure ERROR:
:info:configure The bundled extension libnormaliz was explicitly requested but failed to configure.
:info:configure Please recheck your argument (--with-libnormaliz=/opt/local) and build/bundled.log .
:info:configure You can also disable it by specifying --without-libnormaliz instead.
:info:configure Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_math_polymake/polymake/work/polymake-4.11" && ./configure --prefix=/opt/local --with-boost=/opt/local/libexec/boost/1.76 --with-gmp=/opt/local --with-mpfr=/opt/local --with-cdd=/opt/local --with-lrs=/opt/local --with-permlib=/opt/local --with-libnormaliz=/opt/local --with-sympol=/opt/local --with-mongoc=/opt/local --without-java --without-nauty PERL=/opt/local/bin/perl5.34 
:info:configure Exit code: 25
:error:configure Failed to configure polymake: configure failure: command execution failed

Attachments (1)

main.log (209.8 KB) - added by murrayE 3 months ago.
main.log

Download all attachments as: .zip

Change History (5)

Changed 3 months ago by murrayE

Attachment: main.log added

main.log

comment:1 Changed 3 months ago by ryandesign (Ryan Carsten Schmidt)

It's not mentioned in this main.log, which is unusual, but usually a configure script creates a config.log file somewhere in the work directory, and if something fails during configuration, then the config.log tells us why. If you can find this log, please attach it.

comment:2 in reply to:  1 Changed 3 months ago by catap (Kirill A. Korinsky)

Replying to ryandesign:

It's not mentioned in this main.log, which is unusual, but usually a configure script creates a config.log file somewhere in the work directory, and if something fails during configuration, then the config.log tells us why. If you can find this log, please attach it.

Well, polymake has it's own configure system which doesn't produce it.

I never tries to build it on macOS 14 / arm64, probably it is broke somehow.

comment:3 Changed 3 months ago by ryandesign (Ryan Carsten Schmidt)

Cc: catap removed
Owner: set to catap
Status: newassigned
Summary: polymake-4.11 configure fails - issue with libnormalizpolymake @4.11: bundled extension libnormaliz ... failed

According to buildbot logs, it doesn't build on macOS 14 x86_64 either, nor on macOS 10.14 and earlier. I'm rerunning builds there to generate fresh logs.

comment:4 in reply to:  3 Changed 3 months ago by ryandesign (Ryan Carsten Schmidt)

Replying to ryandesign:

I'm rerunning builds there to generate fresh logs.

None of them failed in the way that Murray reported here. Most failed either because dependencies (mumps or parmetis or scip or onetbb) did not build. Some failed because of error: use of undeclared identifier '__builtin_FUNCTION'. One failed because of:

bundled extension polydb ... failed

ERROR:
The bundled extension polydb was explicitly requested but failed to configure.
Please recheck your argument (--with-polydb=) and build/bundled.log .
You can also disable it by specifying --without-polydb instead.
Note: See TracTickets for help on using tickets.