Your message dated Wed, 28 May 2014 21:37:54 -0400
with message-id <20140529013754.GA5745@helmut>
and subject line Re: Bug#749586: liburcu uses armv7 compiler flags if
buildsystem is armv7
has caused the Debian Bug report #749586,
regarding liburcu uses armv7 compiler flags if buildsystem is armv7
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 [email protected]
immediately.)
--
749586: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749586
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: liburcu
Version: 0.8.4-2.1
Severity: serious
If your package is built on a system with an armv7 processor it builds
for armv7. Since debian armel targets armv4t but is now built on armv7
hardware this is a major prboem. It's also a problem for rasbian.
Also I notice the flags are selecting coretex-a9 specficially rather
than a generic armv7-a. I don't know if that is a problem on debian
armhf or not (that is I don't know if there are any instructions
specific to that core that are not available more generally)
The attatched patch disables the offending flags completely. It has been
uploaded to raspbian, no intent to nmu in Debian.
diff -Nru liburcu-0.8.4/debian/changelog liburcu-0.8.4/debian/changelog
--- liburcu-0.8.4/debian/changelog 2014-05-23 07:35:08.000000000 +0000
+++ liburcu-0.8.4/debian/changelog 2014-05-28 08:35:38.000000000 +0000
@@ -1,3 +1,9 @@
+liburcu (0.8.4-2.1+rpi1) jessie-staging; urgency=low
+
+ * Disable use of armv7 options in configure.ac
+
+ -- Peter Michael Green <[email protected]> Mon, 23 Sep 2013 17:10:40
+0000
+
liburcu (0.8.4-2.1) unstable; urgency=high
* Non-maintainer upload
diff -Nru liburcu-0.8.4/debian/patches/no-armv7-flags.patch
liburcu-0.8.4/debian/patches/no-armv7-flags.patch
--- liburcu-0.8.4/debian/patches/no-armv7-flags.patch 1970-01-01
00:00:00.000000000 +0000
+++ liburcu-0.8.4/debian/patches/no-armv7-flags.patch 2014-05-28
08:36:57.000000000 +0000
@@ -0,0 +1,24 @@
+Description: Don't pass armv7 options
+ The configure script detects the cpu of the build system and if it is armv7
+ proceeds to pass armv7 options to the compiler thus causing use of
+ inappropriate options when an armv7 machine is used to build packages for
+ a port targetting a lower arm CPU. This patch disables that behavious
+Author: Peter Michael Green <[email protected]>
+
+Index: liburcu-0.8.4/configure.ac
+===================================================================
+--- liburcu-0.8.4.orig/configure.ac 2014-05-28 08:36:49.000000000 +0000
++++ liburcu-0.8.4/configure.ac 2014-05-28 08:36:49.000000000 +0000
+@@ -92,9 +92,9 @@
+ AC_DEFINE([CONFIG_RCU_COMPAT_ARCH], [1])
+ ])
+
+-AS_IF([test "$host_cpu" = "armv7l"],[
+- CFLAGS="$CFLAGS -mcpu=cortex-a9 -mtune=cortex-a9 -O1"
+-])
++#AS_IF([test "$host_cpu" = "armv7l"],[
++# CFLAGS="$CFLAGS -mcpu=cortex-a9 -mtune=cortex-a9 -O1"
++#])
+
+ # ARM-specific checks
+ AS_IF([test "x$ARCHTYPE" = "xarm"],[
diff -Nru liburcu-0.8.4/debian/patches/series
liburcu-0.8.4/debian/patches/series
--- liburcu-0.8.4/debian/patches/series 2014-05-23 07:35:08.000000000 +0000
+++ liburcu-0.8.4/debian/patches/series 2014-05-28 08:35:38.000000000 +0000
@@ -1 +1,2 @@
ignore-gcc-check.patch
+no-armv7-flags.patch
--- End Message ---
--- Begin Message ---
* peter green <[email protected]> wrote:
> Package: liburcu
> Version: 0.8.4-2.1
> Severity: serious
>
> If your package is built on a system with an armv7 processor it
> builds for armv7. Since debian armel targets armv4t but is now built
> on armv7 hardware this is a major prboem. It's also a problem for
> rasbian.
This has been fixed in today's upload of version 0.8.4-3. I removed the
explicit call to configure in favor of debhelper. This results in
a correct --build paramater passed to configure, which then correctly
builds the package for the arm target. Build logs are here:
https://buildd.debian.org/status/fetch.php?pkg=liburcu&arch=armel&ver=0.8.4-3&stamp=1401314750
> Also I notice the flags are selecting coretex-a9 specficially rather
> than a generic armv7-a. I don't know if that is a problem on debian
> armhf or not (that is I don't know if there are any instructions
> specific to that core that are not available more generally)
Since debhelper passes the correct --build parameter, configure does not
incorrectly identify the target as armv7l, and thus does not add these
flags. armhf looks correct to me as well:
https://buildd.debian.org/status/fetch.php?pkg=liburcu&arch=armhf&ver=0.8.4-3&stamp=1401316925
If I missed something, please let me know.
Cheers,
--
Jon
--- End Message ---
