Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 406724 Details for
Bug 554808
dev-util/valgrind: configure: error: Valgrind requires glibc version 2.2 - 2.19
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
build.log
dev-util:valgrind-3.10.1:20150713-231513.log (text/plain), 5.69 KB, created by
om3i
on 2015-07-14 00:48:52 UTC
(
hide
)
Description:
build.log
Filename:
MIME Type:
Creator:
om3i
Created:
2015-07-14 00:48:52 UTC
Size:
5.69 KB
patch
obsolete
> * Package: dev-util/valgrind-3.10.1 > * Repository: gentoo > * Maintainer: blueness@gentoo.org > * USE: abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU > * FEATURES: preserve-libs sandbox userpriv usersandbox >>>> Unpacking source... >>>> Unpacking valgrind-3.10.1.tar.bz2 to /var/tmp/portage/dev-util/valgrind-3.10.1/work >>>> Source unpacked in /var/tmp/portage/dev-util/valgrind-3.10.1/work >>>> Preparing source in /var/tmp/portage/dev-util/valgrind-3.10.1/work/valgrind-3.10.1 ... > * Applying valgrind-3.7.0-respect-flags.patch ... > [ ok ] > * Applying valgrind-3.7.0-fno-stack-protector.patch ... > [ ok ] > * Applying valgrind-3.6.0-local-labels.patch ... > [ ok ] > * Applying valgrind-3.10.1-non-exec-stack.patch ... > [ ok ] > * Applying valgrind-3.9.0-glibc-2.19.patch ... > [ ok ] > * Applying valgrind-3.10.1-linux-4.patch ... > [ ok ] > * Running eautoreconf in '/var/tmp/portage/dev-util/valgrind-3.10.1/work/valgrind-3.10.1' ... > * Running aclocal ... > [ ok ] > * Running autoconf --force ... > [ ok ] > * Running autoheader ... > [ ok ] > * Running automake --add-missing --copy --foreign --force-missing ... > [ ok ] > * Running elibtoolize in: valgrind-3.10.1/ >>>> Source prepared. >>>> Configuring source in /var/tmp/portage/dev-util/valgrind-3.10.1/work/valgrind-3.10.1 ... > * econf: updating valgrind-3.10.1/config.guess with /usr/share/gnuconfig/config.guess > * econf: updating valgrind-3.10.1/config.sub with /usr/share/gnuconfig/config.sub >./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-tracking --libdir=/usr/lib64 --without-mpicc >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 make supports nested variables... 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 whether the C compiler works... yes >checking for C compiler default output file name... a.out >checking for suffix of executables... >checking whether we are cross compiling... no >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 whether x86_64-pc-linux-gnu-gcc understands -c and -o together... yes >checking for style of include used by make... GNU >checking dependency style of x86_64-pc-linux-gnu-gcc... none >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++... none >checking for x86_64-pc-linux-gnu-ranlib... x86_64-pc-linux-gnu-ranlib >checking for a sed that does not truncate output... /bin/sed >checking for perl... /usr/bin/perl >checking for gdb... /usr/bin/gdb >checking dependency style of x86_64-pc-linux-gnu-gcc... none >checking for diff -u... yes >checking for a supported version of gcc... ok (5.1.0) >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 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.x/3.x family (4.2.0-rc1) >checking for 32 bit build support... yes >checking for a supported CPU/OS combination... ok (amd64-linux) >checking for use as an inner Valgrind... no >checking for Pagesize... 4k >checking for grep that handles long lines and -e... /bin/grep >checking for egrep... /bin/grep -E >checking for ANSI C header files... yes >checking for sys/types.h... yes >checking for sys/stat.h... yes >checking for stdlib.h... yes >checking for string.h... yes >checking for memory.h... yes >checking for strings.h... yes >checking for inttypes.h... yes >checking for stdint.h... yes >checking for unistd.h... yes >checking features.h usability... yes >checking features.h presence... yes >checking for features.h... yes >checking the GLIBC_VERSION version... unsupported version 2.21 >configure: error: Valgrind requires glibc version 2.2 - 2.19 > >!!! Please attach the following file when seeking support: >!!! /var/tmp/portage/dev-util/valgrind-3.10.1/work/valgrind-3.10.1/config.log > * ERROR: dev-util/valgrind-3.10.1::gentoo failed (configure phase): > * econf failed > * > * Call stack: > * ebuild.sh, line 93: Called src_configure > * environment, line 3066: Called econf '--without-mpicc' > * phase-helpers.sh, line 662: Called __helpers_die 'econf failed' > * isolated-functions.sh, line 117: Called die > * The specific snippet of code: > * die "$@" > * > * If you need support, post the output of `emerge --info '=dev-util/valgrind-3.10.1::gentoo'`, > * the complete build log and the output of `emerge -pqv '=dev-util/valgrind-3.10.1::gentoo'`. > * The complete build log is located at '/var/log/portage/dev-util:valgrind-3.10.1:20150713-231513.log'. > * For convenience, a symlink to the build log is located at '/var/tmp/portage/dev-util/valgrind-3.10.1/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/portage/dev-util/valgrind-3.10.1/temp/environment'. > * Working directory: '/var/tmp/portage/dev-util/valgrind-3.10.1/work/valgrind-3.10.1' > * S: '/var/tmp/portage/dev-util/valgrind-3.10.1/work/valgrind-3.10.1'
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 554808
: 406724 |
406726
|
428312