valgrind fails to build from source in maverick (glibc 2.12)

Bug #602132 reported by Matthias Klose
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
valgrind (Ubuntu)
Fix Released
High
Loïc Minier
Maverick
Fix Released
High
Loïc Minier

Bug Description

Binary package hint: valgrind

fails to build from source with glibc-2.12:

checking for egrep... /bin/grep -E
checking the GLIBC_VERSION version... unsupported version
configure: error: Valgrind requires glibc version 2.2 - 2.11
make: *** [config.status] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Related branches

Matthias Klose (doko)
Changed in valgrind (Ubuntu Maverick):
importance: Undecided → High
milestone: none → maverick-alpha-3
status: New → Confirmed
Barry Warsaw (barry)
Changed in valgrind (Ubuntu Maverick):
assignee: nobody → Barry Warsaw (barry)
Revision history for this message
Loïc Minier (lool) wrote :

You might want to take a new upstream snapshot since upstream supports that version now.

Last time I did that, building the docs was borken and required some painful pdftex workarounds.

Revision history for this message
Barry Warsaw (barry) wrote :

Okay, I grabbed upstream's svn as of 2010-07-08 r11212, created an appropriately named tarball, and merged it into lp:ubuntu/valgrind via:

bzr mu --distribution=maverick --version=1:3.6.0~svn20100708-0ubuntu1 ../valgrind_3.6.0~svn20100708.orig.tar.gz

Then I ran ./autogen.sh but I had to delete the symlinks that creates and copied the real files in:

% rm -f compile config.guess config.sub depcomp install-sh missing
% cp /usr/share/automake-1.11/{compile,config.guess,config.sub,depcomp,install-sh,missing} .

I then disabled the 01_pcm-ioctl, 01_more-vg-n-threads, and 80_splice_backport patches as these appear to be in the svn trunk by now.

The package now appears to build successfully on Maverick. I pushed the branch and will merge-propose it when that shows up. Hopefully this is the correct way to merge in a new upstream svn for valgrind.

Changed in valgrind (Ubuntu Maverick):
status: Confirmed → In Progress
status: In Progress → Fix Committed
Revision history for this message
Loïc Minier (lool) wrote :

 So frankly, I am not sure I can review the full diff you have in the
 merge request, but I can review the instructions in LP #602132.

 I think you could have done an autoreconf -fi instead of ./autogen.sh
 and would have avoided the symlink issue, but I didn't check whether
 autoreconf passes on valgrind tip.

 Disabling the patches was the right thing to do as I pushed them all
 upstream, and all got merged indeed.

 So what I roughly recall I did last time:
   svn export -r somerev
   autoreconf -fi or so to bootstrap autotools files
   ./configure
   make BUILD_ALL_DOCS=no dist
   (make distcheck doesn't pass and was hard to fix)

 then uupdated to the new tarball.

 The BUILD_ALL_DOCS=no disables some docs because the build was broken
 due to some pdftex regression; I discovered a workaround later in the
 form of using the attached pdftex.def on your local machine. See
 Debian #566591; this seems fixed properly now.

 I prefer rolling a tarball because I find it painful to cleanup after
 autogen.sh in debian/rules, and I don't like shipping autofoo files in
 the .diff.gz, but your approach is valid as well.

Revision history for this message
Martin Pitt (pitti) wrote :

Doesn't block the alpha-3 release, it does not cause uninstallability. Moving to beta.

Changed in valgrind (Ubuntu Maverick):
milestone: maverick-alpha-3 → ubuntu-10.10-beta
Revision history for this message
Loïc Minier (lool) wrote :

I wanted to have a valgrind with docs and a real base tarball; also I have some ARM/Thumb related patches I'd like to include, so I wanted to pick a quite specific recent snapshot (just before the THUMB branch was opened).

I did so now, and it seems to have worked fine; I have included my notes in creating the snapshot in the package itself, and have simply uupdated + updated packaging and patches for the new version, it seems to work alright.

Changed in valgrind (Ubuntu Maverick):
assignee: Barry Warsaw (barry) → Loïc Minier (lool)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package valgrind - 1:3.6.0~svn20100724-0ubuntu1

---------------
valgrind (1:3.6.0~svn20100724-0ubuntu1) maverick; urgency=low

  * New upstream snapshot.
    - Supports GLIB 2.12; LP: #602132.
    - Drop dpatch 01_pcm-ioctl; fixed upstream slighlty differently; see
      KDE #227325.
    - Drop dpatch 01_more-vg-n-threads; merged upstream.
    - Drop dpatch 80_splice_backport; merged upstream.
    - Update dpatch 99-autoreconf.
    - Update documentation on creating snapshots in debian/copyright and add
      debian/valgrind-docs-build.diff to help creating these (works around an
      issue with building the docs during make dist).
 -- Loic Minier <email address hidden> Sun, 15 Aug 2010 10:54:00 +0200

Changed in valgrind (Ubuntu Maverick):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.