tached patch should fix this and
work with both old and new Singular versions.
Best,
Benjamin
commit 4ce0549f510d246c8f69c85c509fc2d13d882442
Author: Benjamin Lorenz
Date: Thu Nov 9 11:15:06 2023 +0100
singular: support new return types for saturation command
This was changed from
Dear David,
we have now managed to work around the perl changes and released
polymake version 4.11 which restores compatibility with perl 5.38.
Among various other adjustments the workaround relies on an
auto-generated perl source file that was is now copied into the polymake
source.
This
On 02/10/2023 08.46, Joachim Zobel wrote:
Am Sonntag, dem 01.10.2023 um 15:30 -0300 schrieb David Bremner:
I'm currently waiting to see what happens with
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042521
before putting much effort into debugging polymake issues.
The discussion
Hi,
the attached patch should fix the build with perl 5.36:
- adapt to renamed HVhek_UNSHARED
- adjust for changes in the complement operation
Best,
Benjamin Lorenz
On 03/07/2022 16.33, Niko Tyni wrote:
Source: polymake
Version: 4.6-3
Tags: ftbfs
User: debian-p...@lists.debian.org
Usertags
On 21/12/2021 17.49, Lucas Nussbaum wrote:
[ /polytope/objects/Polytope/properties/Geometry/SLACK_IDEAL ] 1 ? cannot
open `standard.lib`
// ** Could not get 'Singular'.
// ** Either set environment variable 'SINGULAR_EXECUTABLE' to 'Singular',
// ** or make sure that 'Singular' is at
On 31/08/2021 17.29, David Bremner wrote:
This package fails to build from source with Perl 5.34 (currently
in experimental). I don't presently understand why; I'm not aware of
changes to Perl_pp_keys or Perl_pp_rv2hv. So the root issue might also
be on the Perl side. At least it seems to
Dear Joachim,
thanks for the report,
F12 displays a warning
"THREE.OrbitControls: As part of the transition to ES6 Modules, the files in
'examples/js' were deprecated in May 2020 (r117) and will be deleted in
December 2020 (r124)...
these warnings can be ignored as we ship pre-r124 versions
Hello David,
On 28/01/2021 12.59, David Bremner wrote:
The relevant output from the tests seems to be
[ /polytope/objects/Polytope/properties/Triangulation and volume/RELATIVE_VOLUME ] 1polymake:
WARNING: rule RELATIVE_VOLUME : SQUARED_RELATIVE_VOLUMES failed: Undefined subroutine
On 13/02/2020 16.53, Benjamin Lorenz wrote:
> On 13/02/2020 13.18, David Bremner wrote:
>> Benjamin Lorenz writes:
>>>> It looks like it's flint related?
>>>
>>> Yes, I think this is a bug in flint and for now I suggest disabling the
>>> flint
On 13/02/2020 13.18, David Bremner wrote:
> Benjamin Lorenz writes:
>
>>
>>> It looks like it's flint related?
>>
>> Yes, I think this is a bug in flint and for now I suggest disabling the
>> flint-interface of polymake with the configure option --without-f
On 11/02/2020 16.22, Gianfranco Costamagna wrote:
> Hello, looks like with TERM=unknown the testsuite fails:
>
> *** Failed tests ***
>
> /<>/apps/common/rules/functions_help.rules:248: testcase 1
> expected: regular return
> got: EXCEPTION: Can't find a valid termcap file at
>
After some time of setting this up and building I can reproduce it and
got a better backtrace which seems well inside flint (up to frame 6):
Program received signal SIGSEGV, Segmentation fault.
0x0040014cb29c in flint_mpz_set_ui (r=0x400c8e3dd0, r=0x400c8e3dd0,
u=9223372036854775837)
at
On 26/11/2019 01.51, Andreas Beckmann wrote:
> On 26/11/2019 00.00, Benjamin Lorenz wrote:
>> tldr: please rebuild normaliz and then try polymake again.
>
> Thanks for the analysis. binNMU of normaliz requested: #945504
Thanks.
>> This is very weird but after some diggi
On 23/11/2019 20.30, Andreas Beckmann wrote:
> Control: affects 941933 + src:polymake
> Control: retitle -1 polymake: FTBFS with normaliz 3.8.1: segfaults during
> tests
>
> On 23/11/2019 10.45, Benjamin Lorenz wrote:
>> On 22/11/2019 22.06, Andreas Beckmann wrote:
>&
On 22/11/2019 22.06, Andreas Beckmann wrote:
> polymake FTBFS against perl 5.30:
> https://buildd.debian.org/status/package.php?p=polymake=unstable
>
> *** Summary ***
>
> *** Failed tests ***
>
> /<>/apps/polytope/src/gc_closure.cc:173: testcase 1
> expected: regular return
> got:
On 10/7/19 8:30 PM, Niko Tyni wrote:
> On Mon, Oct 07, 2019 at 08:59:47PM +0300, Niko Tyni wrote:
>> Source: polymake
>> Version: 3.2r4-4
>> Severity: serious
>> Tags: ftbfs
>> Control: block 935737 with -1
>>
>> This package failed to build in sid when rebuilding against Perl 5.30.
>>
>> Looking
Hi,
thanks for the report! We already have a patch included in polymake
3.2r3 and 3.2r4 that fixes the build error and keeps compatibility with
older boost versions. (And also added another change there to avoid a
depreciation warning for math::lcm)
I have tried updating the package here:
Hi,
this comes from a different output order produced by cdd version 0.94j
(probably caused by https://github.com/cddlib/cddlib/pull/10 ).
We have disabled this test in polymake 3.2r4. I have tried updating the
package and created a pull request here:
Dear Lev,
It seems a fix for this bug was merged into the upstream stable
repository some time ago:
https://github.com/SWI-Prolog/swipl/commit/3923765d56e5
I have an unstable i386 VM where I could reproduce these memory errors
and adding this to the patches resolves it.
Since there is still no
created a pull request to for this:
https://github.com/SWI-Prolog/packages-jpl/pull/8
I have tried this on i386 and the package now compiles but make check
then fails with the same errors as in #887155.
Regards,
Benjamin Lorenz
On 01/06/2018 08:08 PM, Niko Tyni wrote:
> Running polymake currently fails with
>
> $ polymake
> Can't locate loadable object for module Polymake::Ext in @INC
>
> Apparently this is because it was built with Perl 5.26.0, but
> we've since moved to 5.26.1.
>
> I see two better alternatives:
>
On 25/08/16 19:59, David Bremner wrote:
> Dominic Hargreaves writes:
>
>>
>> This bug will become RC when the perl package change removing '.' from
>> @INC by default is uploaded to unstable, expected in a week or two.
>>
>> By the way, when preparing this patch I found that the
are probably optimization bugs in gcc and will be
investigated soon.
Benjamin Lorenz
On 20/01/16 15:24, David Bremner wrote:
> Is the updated version (or equivalent) in 3.0? Since I let it slide this
> long, I was thinking of just uploading 3.0 instead.
Yes, the updated patch is included in version 3.0.
Best,
Benjamin
The previous patch caused a small build issue on some configurations
which probably does not affect debian. A corrected patch is attached now.
Regards,
Benjamin
diff --git a/perllib/Polymake/Configure.pm b/perllib/Polymake/Configure.pm
index 8f87e49..f890ac8 100644
---
The patch for 2.14r1 is attached.
Regards,
Benjamin
diff --git a/perllib/Polymake/Configure.pm b/perllib/Polymake/Configure.pm
index 8f87e49..f890ac8 100644
--- a/perllib/Polymake/Configure.pm
+++ b/perllib/Polymake/Configure.pm
@@ -268,7 +268,7 @@ sub write_conf_vars {
no strict 'refs';
Sending the attachment manually as it didn't come with the notification.
Benjamin Lorenz
>From f293923ae20196f34b1348bae9338fed0387388c Mon Sep 17 00:00:00 2001
From: Christof Soeger <csoe...@uos.de>
Date: Tue, 8 Dec 2015 12:04:40 +0100
Subject: [PATCH] fix libnormaliz for gmp 6.1
ada
Hi,
We have recently released a bugfix release for 2.14 [1], which includes
support for perl 5.22 and also a fix for an issue with gcc 5.1.
[1]: http://polymake.org/doku.php/download/start
Best,
Benjamin
28 matches
Mail list logo