Opened 3 years ago

Last modified 3 years ago

#21625 closed enhancement

Strange linking order for omalloc — at Version 3

Reported by: jpflori Owned by:
Priority: major Milestone: sage-7.5
Component: packages: standard Keywords:
Cc: Merged in:
Authors: Reviewers:
Report Upstream: Fixed upstream, in a later stable release. Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Description (last modified by jdemeyer)

This is a follow up to #17254 which upgraded to singular 4:

The linking order for Singular libraries is determined by pkgconfig which gives

-lomalloc -lSingular -lpolys -lfactory -lresources

This does not look that right.

Change History (3)

comment:1 in reply to: ↑ description Changed 3 years ago by jdemeyer

  • Summary changed from Starnge linking order for omalloc to Strange linking order for omalloc

Replying to jpflori:

This is a follow up to #17254 which upgraded to singular 4:

  • strange linking order (omalloc comes before singular!)

You mean during the build of Singular itself or Sage modules using Singular?

comment:2 Changed 3 years ago by jpflori

See https://trac.sagemath.org/ticket/17254#comment:510 : """ During linking some Sage files I see -lomalloc -lSingular -lpolys -lfactory -lresources which does not look that right. """

comment:3 Changed 3 years ago by jdemeyer

  • Description modified (diff)
  • Milestone changed from sage-7.4 to sage-7.5
Note: See TracTickets for help on using tickets.