[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#826251: marked as done (fwupd FTBFS on mips)

Your message dated Wed, 7 Sep 2016 19:56:09 +0000
with message-id <31d1985f3a4c4a3ebc0fab293a35339f@ausx13mpc124.AMER.DELL.COM>
and subject line 
has caused the Debian Bug report #826251,
regarding fwupd FTBFS on mips
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
826251: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826251
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: fwupd
Version: 0.7.0-1
Severity: normal
Tags: sid + patch
Justification: FTBFS
User: debian-mips@lists.debian.org
Usertags: mips-patch

Hello,

Package fwupd_0.7.0-1 FTBFS on mips with following error:
VEX: Unsupported baseline
     Found: Cavium-baseline
Cannot continue. Good-bye

vex storage: T total 0 bytes allocated
vex storage: P total 0 bytes allocated

valgrind: the 'impossible' happened:
   LibVEX called failure_exit().


build log:
https://buildd.debian.org/status/fetch.php?pkg=fwupd&arch=mips&ver=0.7.0-1&stamp=1461193596

This issue is caused by valgrind which does not have support for cavium cores in version which is installed in Debian archive.

Until cavium is supported is it possible to disable execution of valgrind on mips,
or to build this package on some other non cavium mips build-machine, if any is available?

This is issue is already noticed for package colorhug-client	
and resolved by not using valgrind on mips:
colorhug-client (0.2.8-2) unstable; urgency=medium

  * Do not try to use valgrind for testing on mips, it seems to be broken.
  * Bump standards to 3.9.7.

 -- Michal Čihař <nijel@debian.org>  Thu, 07 Apr 2016 13:15:38 +0200


I have attached a patch that disable valgind usage during package build on mips.
With patch package was built successfully from source.

Thank you!

Regards,
Jurica
diff -upNr fwupd-0.7.0-orig/debian/control fwupd-0.7.0/debian/control
--- fwupd-0.7.0-orig/debian/control	2016-04-16 00:03:45.000000000 +0000
+++ fwupd-0.7.0/debian/control	2016-06-03 14:57:25.000000000 +0000
@@ -29,7 +29,7 @@ Build-Depends: debhelper (>= 9.0.0),
                libsoup2.4-dev,
                gtk-doc-tools,
                libcolorhug-dev,
-               valgrind
+               valgrind[!mips]
 Standards-Version: 3.9.7
 Section: admin
 Homepage: https://github.com/hughsie/fwupd
diff -upNr fwupd-0.7.0-orig/debian/rules fwupd-0.7.0/debian/rules
--- fwupd-0.7.0-orig/debian/rules	2016-04-19 00:29:16.000000000 +0000
+++ fwupd-0.7.0/debian/rules	2016-06-03 15:04:19.000000000 +0000
@@ -32,5 +32,7 @@ override_dh_install:
 	dh_install --fail-missing
 
 override_dh_auto_test:
-	HOME=`pwd` dh_auto_test
-	HOME=`pwd` gpg-connect-agent "KILLAGENT" /bye
+	if [ -x /usr/bin/valgrind ] ; then \
+		HOME=`pwd` dh_auto_test ; \
+		HOME=`pwd` gpg-connect-agent "KILLAGENT" /bye ; \
+	fi

--- End Message ---
--- Begin Message ---

Package: fwupd

Version: 0.7.2-1

 

Thanks for the patch.  I included it in the previous upload before the most recent but used the wrong syntax to close the bug. (Fixes vs Closes)

 

 


--- End Message ---
Reply to: