Ticket #1611 (closed enhancement: fixed)

Opened 5 years ago

Last modified 4 years ago

polybori should use the m4ri library from libm4ri spkg

Reported by: burcin Owned by: burcin
Priority: major Milestone: sage-4.1.2
Component: packages: standard Keywords:
Cc: PolyBoRi Work issues:
Report Upstream: Reviewers:
Authors: Merged in:
Dependencies: Stopgaps:

Description

PolyBoRi? comes with its own copy of m4ri libraries. After #1505, Sage provides these libraries through a package.

The PolyBoRi? build process should be changed to use the library and headers provided by libm4ri-*.spkg.

Change History

comment:1 Changed 5 years ago by malb

Michael Brickenstein wrote:

If you can wait until the end of my holidays, which will begin tomorrow and end at 6th of January, I will do the switch myself.

comment:2 Changed 5 years ago by burcin

  • Status changed from new to assigned
  • Milestone changed from sage-2.9.2 to sage-2.10

comment:3 Changed 5 years ago by mabshoff

The issue might be resolved during the update to PolyBoRi? 0.2.rcX during Bug Day 10.

Cheers,

Michael

comment:4 Changed 5 years ago by mabshoff

This should be done while updating PolyBori? - see #2060.

Cheers,

Michael

comment:5 Changed 5 years ago by burcin

PolyBoRi requires some changes in the m4ri libraries. They are waiting for changes upstream (in m4ri) to switch over, so newer versions of PolyBoRi don't support this.

comment:6 Changed 5 years ago by malb

I guess I am upstream so I should diff their m4ri against ours (upstream).

comment:7 Changed 5 years ago by mabshoff

Fixing this bug is planned for the PolyBoRi? 0.5 release.

Cheers,

Michael

comment:8 Changed 5 years ago by mabshoff

  • Cc PolyBoRi added

#3264 does not fix the problem yet. Are there any options to make this happen with PolyBoRi? 0.5?

Cheers,

Michael

comment:9 Changed 5 years ago by malb

There is some movement w.r.t. this issue in PolyBoRi?, but I wouldn't suspect it to be available in 0.5.

comment:10 Changed 5 years ago by PolyBoRi

it will be available in 0.5. However, you should make sure, that malloc work also for allocating zero bytes in M4RI, else it will crash (doesn't work with mm_malloc on Mac OS X 10.5).

comment:11 Changed 4 years ago by malb

  • Status changed from assigned to closed
  • Resolution set to fixed

This is fixed with #6177

Note: See TracTickets for help on using tickets.