| Summary: | Valgrind-2.0.0 fails to compile: union has no member named `__m_count` | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Stephen Torri <storri> |
| Component: | [OLD] Development | Assignee: | solar (RETIRED) <solar> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | blocker | CC: | aross |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
Config.log file for valgrind-2.0.0 emerge
Error report from emerge of valgrind. |
||
|
Description
Stephen Torri
2004-07-10 10:51:56 UTC
Works fine for me with same CFLAGS, MAKEOPTS, FEATURES, and {glib,gcc,autoconf,automake} version.
Please post your config.log as an attachment, and I will compare with mine. Perhaps configure is autodetecting something present on your system and missing on mine (or vice versa).
You can find config.log in /var/tmp/portage/valgrind-2.0.0/work/valgrind-2.0.0
I also suggest you change this bug's severity from "normal" to "blocker".
Portage 2.0.50-r9 (default-x86-2004.0, gcc-3.3.3, glibc-2.3.3.20040420-r0, 2.6.7-gentoo-r8)
=================================================================
System uname: 2.6.7-gentoo-r8 i686 Intel(R) Pentium(R) M processor 1.70GHz
Gentoo Base System version 1.4.16
Autoconf: sys-devel/autoconf-2.59-r3
Automake: sys-devel/automake-1.8.3
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-march=pentium3 -pipe"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=pentium3 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs buildpkg ccache fixpackages sandbox strict userpriv"
GENTOO_MIRRORS="ftp://ftp.monash.edu.au/pub/linux/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.au.gentoo.org/gentoo-portage"
USE="X acpi alsa apache2 avi bcmath berkdb cdr crypt cups doc dvd encode esd fam gd gdbm gif gnome gpm gtk gtk2 imap imlib java jikes jpeg libwww mad memlimit mmx motif mozilla mpeg mysql ncurses offensive oggvorbis opengl pam pdflib perl png python quicktime readline samba sdl slang spell sse ssl svg svga theora tiff truetype x86 xml2 xmms xv zlib"
Created attachment 35273 [details]
Config.log file for valgrind-2.0.0 emerge
This file hopefully contains why valgrind does build. Here you go agross.
Changing bug severity to blocker. Thanks Stephen. A diff between our config.logS shows that the only difference is NTPL, which is turned on for you and off for me. Looks like this problem has been reported and addressed upstream - see: http://bugs.kde.org/show_bug.cgi?id=69616 Please try the suggested patch (http://bugs.kde.org/attachment.cgi?id=4618&action=view) - the 2.0.0 ebuild should probably be modified to apply it. Grabbing the patch is not an issue. What do I edit in the ebuild file? I have not made time to learn how to build my own. I don't actually use 2.6-nptl so I can't test or verify said patch resolves anything, but if you need me to add this or another patch from cvs please attach said patch and an ebuild diff that's been tested on on 2.4.x and 2.6.x w & w/o nptl Created attachment 35359 [details]
Error report from emerge of valgrind.
I have downloaded what I believe is the patch from bugs.kde.org for valgrind-2.0.0. I edited the valgrind-2.0.0.ebuild file as follows:
src_unpack() {
unpack ${A}
cd ${S}
# if [ `uname -r | awk -F . '{print $2}'` == 6 ]; then
# epatch ${FILESDIR}/${PN}-configure.in-2.6.diff
# autoconf || die "error while running autoconf"
# fi
epatch ${FILESDIR}/${PN}-nptl.patch
}
This should have applied it. Now believe is the result of this when I tried to emerge valgrind-2.0.0:
bash-2.05b$ sudo emerge -v valgrind
Calculating dependencies ...done!
>>> emerge (1 of 1) dev-util/valgrind-2.0.0 to /
>>> md5 src_uri ;-) valgrind-2.0.0.tar.bz2
>>> Unpacking source...
>>> Unpacking valgrind-2.0.0.tar.bz2 to /var/tmp/portage/valgrind-2.0.0/work
* Applying valgrind-nptl.patch...
* Failed Patch: valgrind-nptl.patch!
*
* Include in your bugreport the contents of:
*
* /var/tmp/portage/valgrind-2.0.0/temp/valgrind-nptl.patch-16166.out
!!! ERROR: dev-util/valgrind-2.0.0 failed.
!!! Function epatch, Line 322, Exitcode 0
!!! Failed Patch: valgrind-nptl.patch!
Attached is the result file:
From looking at the failed error report of patching I assume that patch is to cvs and 2.0.0 is just to far off with offsets for it to patch correctly. So... maybe fixed in 2.0.1 whenever that will be released. In that case, should the current ebuild at least be modified to abort (eg. with error) when users have nptl in their USE? Otherwise, users may start reporting duplicates of this bug. Andrew, It probably should, but unfortunately the package lacks a proper enthusiastic maintainer and I'd just assume wait for the next release before I have to go poking around in the internals of the ebuild for one last revision. fixed long ago; upgrade your valgrind *** This bug has been marked as a duplicate of 32966 *** Thanks for pointing out the dupe, vapier. I erroneously assumed that searching open bugs would be sufficient, since any resolved bug would obviously result in a working ebuild (or appropriate warning, as suggested by myself in this bug). However, I am puzzled by your curt dismissal of this issue. Your comment of "update your valgrind" is suggesting that users update not only to an unstable ebuild, but an unstable upstream release. According to http://valgrind.kde.org/downloads.html, the current stable version of valgrind is 2.0.0 clearly what upstream calls stable and reality of the matter differ as this bug here proves. |
