Opened 10 years ago

Last modified 8 years ago

#13060 closed defect

Valgrind complains about glibc 2.15 — at Version 2

Reported by: jpflori Owned by: tbd
Priority: major Milestone: sage-5.13
Component: packages: optional Keywords: valgrind spkg
Cc: iandrus, jpflori, schilly Merged in:
Authors: Reviewers:
Report Upstream: Fixed upstream, but not in a stable release. Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description (last modified by jpflori)

Valgrind configure script complains about glibc version 2.15 (which is shipped e.g. with Ubuntu 12.04).

The usual solution is to treat this version as the previous one: see commit r12323 in the valgrind svn, or tickets on different distribution bug tracker.

Furthermore, the autogen.sh scripts fails with recent automake version. This is commit r12396.

An updated spkg including these two commits on top of 3.7.0 is available at http://perso.telecom-paristech.fr/~flori/sage/valgrind-3.7.0.p0.spkg

Change History (3)

comment:1 Changed 10 years ago by jpflori

After applying the diff of the above commit, one has to rebuild the configure scripts with autogen.sh (which is available in the svn, not in the usual tarballs). This basically calls auto* stuff, but the current input *.am files are incompatible with the current automake tool... See r12396 in valgrind svn.

comment:2 Changed 10 years ago by jpflori

  • Description modified (diff)
  • Status changed from new to needs_review

Here comes a slightly updated spkg: http://perso.telecom-paristech.fr/~flori/sage/valgrind-3.7.0.p0.spkg

I've applied the two mentioned patches and rerun autogen.sh to regenerate the build system files. The package installs and seems functional with my Sage installation.

Another solution whould be to properly package a recent valgrind svn version, although I'd prefer to use this light solution and wait for a proper stable release to make a real update to valgrind. Feel free to disagree and rant here.

Changed 10 years ago by jpflori

Spkg diff, for review only.

Note: See TracTickets for help on using tickets.