Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
Valgrind requires the older glibc to build, must be updated Reproducible: Always Steps to Reproduce: 1.emerge valgrind 2.configure: error: Valgrind requires glibc version 2.2 - 2.5 3. Expected Results: should be fixed to build with newest glibc, not sure what effect will now have on new testing system
Created an attachment (id=125050) [details] Patch to add glibc-2.6 support
Created an attachment (id=125052) [details] ebuild patch to apply glibc patch
(In reply to comment #1) > Created an attachment (id=125050) [edit] [details] > Patch to add glibc-2.6 support There's useless config.log in this patch :) .
Created an attachment (id=125130) [details] The corrected patch Oops *blush*
Kevin, Thanks for repairing this so quickly but Im just not sure of how to use this, Am I trying to apply a patch against the ebuild or what exactly, Im not real swift at patching, What exactly do I do?
Okay, Heres what I did ebuild /usr/portage/dev-util/valgrind/valgrind-3.2.3.ebuild unpack wget -qO- 'http://bugs.gentoo.org/attachment.cgi?id=125130' | \ patch -p1 -d /var/tmp/portage/dev-util/valgrind-3.2.3/work/valgrind-3.2.3/ ebuild /usr/portage/dev-util/valgrind/valgrind-3.2.3.ebuild merge clean I remembered patching a different file one time and adjusted the commands for valgrind but it still didnt emerge ebuild /usr/portage/dev-util/valgrind/valgrind-3.2.3.ebuild merge clean Disabling noauto in features... merge disables it. (qmerge doesn't) * valgrind-3.2.3.tar.bz2 MD5 ;-) ... [ ok ] * valgrind-3.2.3.tar.bz2 RMD160 ;-) ... [ ok ] * valgrind-3.2.3.tar.bz2 SHA1 ;-) ... [ ok ] * valgrind-3.2.3.tar.bz2 SHA256 ;-) ... [ ok ] * valgrind-3.2.3.tar.bz2 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking valgrind-3.2.3.tar.bz2 ;-) ... [ ok ] >>> Checking valgrind-3.2.3.tar.bz2's mtime... >>> WORKDIR is up-to-date, keeping... >>> Compiling source in /var/tmp/portage/dev-util/valgrind-3.2.3/work/valgrind-3.2.3 ... * econf: updating valgrind-3.2.3/config.guess with /usr/share/gnuconfig/config.guess * econf: updating valgrind-3.2.3/config.sub with /usr/share/gnuconfig/config.sub ./configure --prefix=/usr --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --with-x --libdir=/usr/lib64 --build=x86_64-pc-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking whether ln -s works... yes checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of x86_64-pc-linux-gnu-gcc... gcc3 checking how to run the C preprocessor... x86_64-pc-linux-gnu-gcc -E checking for x86_64-pc-linux-gnu-g++... x86_64-pc-linux-gnu-g++ checking whether we are using the GNU C++ compiler... yes checking whether x86_64-pc-linux-gnu-g++ accepts -g... yes checking dependency style of x86_64-pc-linux-gnu-g++... gcc3 checking for x86_64-pc-linux-gnu-ranlib... x86_64-pc-linux-gnu-ranlib checking for perl... /usr/bin/perl checking for gdb... /usr/bin/gdb checking dependency style of x86_64-pc-linux-gnu-gcc... gcc3 checking for a supported version of gcc... ok (x86_64-pc-linux-gnu-gcc (GCC) 4.1.2 (Gentoo 4.1.2)) checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking for a supported CPU... ok (x86_64) checking for use as an inner Valgrind... no checking for a 64-bit only build... no checking for a 32-bit only build... no checking for a supported OS... ok (linux-gnu) checking for the kernel version... 2.6 family (2.6.22-gentoo-r1-1) checking for a supported CPU/OS combination... ok (x86_64-linux-gnu) checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking the glibc version... unsupported version configure: error: Valgrind requires glibc version 2.2 - 2.5 !!! Please attach the following file when filing a report to bugs.gentoo.org: !!! /var/tmp/portage/dev-util/valgrind-3.2.3/work/valgrind-3.2.3/config.log * * ERROR: dev-util/valgrind-3.2.3 failed. * Call stack: * ebuild.sh, line 1647: Called dyn_compile * ebuild.sh, line 988: Called qa_call 'src_compile' * ebuild.sh, line 44: Called src_compile * valgrind-3.2.3.ebuild, line 78: Called econf '--with-x' * ebuild.sh, line 591: Called die * * econf failed * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/dev-util/valgrind-3.2.3/temp/build.log'.
(In reply to comment #5) > Kevin, Thanks for repairing this so quickly but Im just not sure of > how to use this, Am I trying to apply a patch against the ebuild > or what exactly, Im not real swift at patching, What exactly do I > do? > Apply the ebuild patch against /usr/portage/dev-util/valgrind-3.2.3.ebuild and copy the other patch into /usr/portage/dev-util/valgrind/files/valgrind-3.2.3-glibc-2.6.patch ebuild /usr/portage/dev-util/valgrind/valgrind-3.2.3.ebuild manifest emerge valgrind
The fix is in portage now. Thanks for reporting this problem.
