valgrind build is broken
Reported by
vpalatin@chromium.org,
Jun 20 2017
|
|||
Issue descriptionTry to build valgrind to deploy on an x86_64 Chrome OS target (e.g. 'emerge-eve valgrind'). No longer works for me, the configuration seems confused between the clang version (5.0.0) and the GCC version (4.9.2), might be the switch to Clang as the default toolchain $ emerge-eve valgrind Calculating dependencies... done! >>> Emerging (1 of 1) dev-util/valgrind-3.10.1::portage-stable for /build/eve/ * valgrind-3.10.1.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * Running stacked hooks for pre_pkg_setup * sysroot_build_bin_dir ... [ ok ] * Running stacked hooks for post_pkg_setup * python_eclass_hack ... [ ok ] * Running stacked hooks for pre_src_unpack * python_multilib_setup ... [ ok ] >>> Unpacking source... >>> Unpacking valgrind-3.10.1.tar.bz2 to /build/eve/tmp/portage/dev-util/valgrind-3.10.1/work >>> Source unpacked in /build/eve/tmp/portage/dev-util/valgrind-3.10.1/work * Running stacked hooks for post_src_unpack * asan_init ... [ ok ] * Running stacked hooks for pre_src_prepare * use_gcc ... [ ok ] >>> Preparing source in /build/eve/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.10.0-glibc-2.23.patch ... [ ok ] * Applying valgrind-3.10.1-linux-4.patch ... [ ok ] * Running eautoreconf in '/build/eve/tmp/portage/dev-util/valgrind-3.10.1/work/valgrind-3.10.1' ... * Running aclocal -I /build/eve/usr/share/aclocal ... [ ok ] * Running autoconf --force -I /build/eve/usr/share/aclocal ... [ ok ] * Running autoheader -I /build/eve/usr/share/aclocal ... [ ok ] * Running automake --add-missing --copy --foreign --force-missing ... [ ok ] * Running elibtoolize in: valgrind-3.10.1/ >>> Source prepared. >>> Configuring source in /build/eve/tmp/portage/dev-util/valgrind-3.10.1/work/valgrind-3.10.1 ... * econf: updating valgrind-3.10.1/config.sub with /usr/share/gnuconfig/config.sub * econf: updating valgrind-3.10.1/config.guess with /usr/share/gnuconfig/config.guess ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-cros-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --disable-silent-rules --disable-dependency-tracking --enable-only64bit --without-mpicc configure: loading site script /usr/share/config.site configure: loading site script /usr/share/crossdev/include/site/linux configure: loading site script /usr/share/crossdev/include/site/linux-gnu configure: loading site script /usr/share/crossdev/include/site/x86_64-linux-gnu checking for a BSD-compatible install... /usr/lib64/portage/bin/ebuild-helpers/xattr/install -c checking whether build environment is sane... yes checking for x86_64-cros-linux-gnu-strip... x86_64-cros-linux-gnu-strip 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-cros-linux-gnu-gcc... x86_64-cros-linux-gnu-clang 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... yes checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether x86_64-cros-linux-gnu-clang accepts -g... yes checking for x86_64-cros-linux-gnu-clang option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of x86_64-cros-linux-gnu-clang... none checking whether x86_64-cros-linux-gnu-clang and cc understand -c and -o together... yes checking how to run the C preprocessor... x86_64-cros-linux-gnu-clang -E checking whether we are using the GNU C++ compiler... yes checking whether x86_64-cros-linux-gnu-clang++ accepts -g... yes checking dependency style of x86_64-cros-linux-gnu-clang++... none checking for x86_64-cros-linux-gnu-ranlib... x86_64-cros-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-cros-linux-gnu-clang... none checking for diff -u... yes checking for a supported version of gcc... no (5.0.0) configure: error: please use gcc >= 3.0 or clang >= 2.9 !!! Please attach the following file when seeking support: !!! /build/eve/tmp/portage/dev-util/valgrind-3.10.1/work/valgrind-3.10.1/config.log * ERROR: dev-util/valgrind-3.10.1::portage-stable failed (configure phase): * econf failed * * Call stack: * ebuild.sh, line 93: Called src_configure * environment, line 3381: Called econf '--enable-only64bit' '--without-mpicc' * phase-helpers.sh, line 584: Called die * The specific snippet of code: * die "econf failed" * * If you need support, post the output of `emerge --info '=dev-util/valgrind-3.10.1::portage-stable'`, * the complete build log and the output of `emerge -pqv '=dev-util/valgrind-3.10.1::portage-stable'`. * The complete build log is located at '/build/eve/tmp/portage/logs/dev-util:valgrind-3.10.1:20170620-083000.log'. * For convenience, a symlink to the build log is located at '/build/eve/tmp/portage/dev-util/valgrind-3.10.1/temp/build.log'. * The ebuild environment file is located at '/build/eve/tmp/portage/dev-util/valgrind-3.10.1/temp/environment'. * Working directory: '/build/eve/tmp/portage/dev-util/valgrind-3.10.1/work/valgrind-3.10.1' * S: '/build/eve/tmp/portage/dev-util/valgrind-3.10.1/work/valgrind-3.10.1' >>> Failed to emerge dev-util/valgrind-3.10.1 for /build/eve/, Log file: >>> '/build/eve/tmp/portage/logs/dev-util:valgrind-3.10.1:20170620-083000.log' * Messages for package dev-util/valgrind-3.10.1 merged to /build/eve/: * ERROR: dev-util/valgrind-3.10.1::portage-stable failed (configure phase): * econf failed * * Call stack: * ebuild.sh, line 93: Called src_configure * environment, line 3381: Called econf '--enable-only64bit' '--without-mpicc' * phase-helpers.sh, line 584: Called die * The specific snippet of code: * die "econf failed" * * If you need support, post the output of `emerge --info '=dev-util/valgrind-3.10.1::portage-stable'`, * the complete build log and the output of `emerge -pqv '=dev-util/valgrind-3.10.1::portage-stable'`. * The complete build log is located at '/build/eve/tmp/portage/logs/dev-util:valgrind-3.10.1:20170620-083000.log'. * For convenience, a symlink to the build log is located at '/build/eve/tmp/portage/dev-util/valgrind-3.10.1/temp/build.log'. * The ebuild environment file is located at '/build/eve/tmp/portage/dev-util/valgrind-3.10.1/temp/environment'. * Working directory: '/build/eve/tmp/portage/dev-util/valgrind-3.10.1/work/valgrind-3.10.1' * S: '/build/eve/tmp/portage/dev-util/valgrind-3.10.1/work/valgrind-3.10.1'
,
Jun 20 2017
,
Jun 20 2017
From the configure in the valgrind, it seems that it does not support clang 5.*, I can try some new valgrind to see whether it works.
case "${is_clang}-${gcc_version}" in
clang-2.9|clang-3.*|clang-4.*)
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: ok (clang-${gcc_version})" >&5
$as_echo "ok (clang-${gcc_version})" >&6; }
;;
*)
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no (${gcc_version})" >&5
$as_echo "no (${gcc_version})" >&6; }
as_fn_error $? "please use gcc >= 3.0 or clang >= 2.9" "$LINENO" 5
;;
esac
,
Jun 21 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/portage-stable/+/c4ade0e59beb2c25ed6df60643df60d5a9cc0882 commit c4ade0e59beb2c25ed6df60643df60d5a9cc0882 Author: Yunlian Jiang <yunlian@google.com> Date: Wed Jun 21 02:30:19 2017 valgrind: upgrade to 3.12 This pulls upstream valgrind-3.12 to make it build with clang-5.0. BUG= chromium:734945 TEST=emerge-terra valgrind works. Change-Id: Ia50eb3cc7b06688b15eecc67cd8813cb3edc4ae0 Reviewed-on: https://chromium-review.googlesource.com/540745 Commit-Ready: Yunlian Jiang <yunlian@chromium.org> Tested-by: Yunlian Jiang <yunlian@chromium.org> Reviewed-by: Manoj Gupta <manojgupta@chromium.org> [delete] https://crrev.com/268a3751ada075be0611a93cb7e690ec50a4f23d/dev-util/valgrind/files/valgrind-3.10.0-glibc-2.23.patch [delete] https://crrev.com/268a3751ada075be0611a93cb7e690ec50a4f23d/dev-util/valgrind/files/valgrind-3.10.1-non-exec-stack.patch [rename] https://crrev.com/c4ade0e59beb2c25ed6df60643df60d5a9cc0882/dev-util/valgrind/valgrind-3.12.0.ebuild [modify] https://crrev.com/c4ade0e59beb2c25ed6df60643df60d5a9cc0882/dev-util/valgrind/Manifest [delete] https://crrev.com/268a3751ada075be0611a93cb7e690ec50a4f23d/dev-util/valgrind/files/valgrind-3.10.1-linux-4.patch [delete] https://crrev.com/268a3751ada075be0611a93cb7e690ec50a4f23d/dev-util/valgrind/files/valgrind-3.6.0-local-labels.patch
,
Jun 21 2017
The updated version works for me Thanks ! |
|||
►
Sign in to add a comment |
|||
Comment 1 by llozano@chromium.org
, Jun 20 2017Owner: yunlian@chromium.org
Status: Assigned (was: Untriaged)