Your message dated Sat, 17 Mar 2012 13:56:11 +0000
with message-id <[email protected]>
and subject line re: gmime2.4 FTBFS on armhf assembler errors from gcc
has caused the Debian Bug report #657685,
regarding gmime2.4 FTBFS on armhf assembler errors from gcc
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.)
--
657685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657685
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
package: gmime2.4
severity: important
tags: patch
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../util -DGMIME_VERSION=\"2.4.31\"
-DGMIME_MAJOR_VERSION=2 -DGMIME_MINOR_VERSION=4 -DGMIME_MICRO_VERSION=31
-DG_LOG_DOMAIN=\"gmime\" -DG_DISABLE_DEPRECATED -D_LARGEFILE64_SOURCE
-D_FILE_OFFSET_BITS=64 -pthread -I/usr/include/glib-2.0
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -g -O2 -fno-strict-aliasing -c gmime-param.c -fPIC
-DPIC -o .libs/gmime-param.o
/tmp/cc1SBNmj.s: Assembler messages:
/tmp/cc1SBNmj.s:2152: Error: can't resolve `.rodata' {.rodata section} -
`.LPIC18' {*UND* section}
make[5]: *** [gmime-param.lo] Error 1
I have produced a somewhat reduced (though not as much as i'd like) testcase
and sent it as a bug report on gcc-4.6[1] but I don't expect a fast response
from them and it's important for the armhf to keep things in sync as much as
possible as we aim towards becoming a release architecture.
The bug is only reproducable with -O2 and higher, it is not reproducable
with -O1.
Therefore could I ask you to apple the attatched patch which reduces the
optmisation level on armhf to -O1 to your next upload (please don't upload
right now though unless you have rc issues to fix, getting the mono
transition through is more important than helping us out).
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657682
--- gmime2.4-2.4.31/debian/rules 2012-01-28 00:01:37.000000000 +0000
+++ gmime2.4-2.4.31.new/debian/rules 2012-01-27 23:48:59.000000000 +0000
@@ -16,6 +16,13 @@
include /usr/share/quilt/quilt.make
include /usr/share/gnome-pkg-tools/1/rules/uploaders.mk
+DEB_HOST_ARCH ?=$(shell dpkg-architecture -qDEB_HOST_ARCH)
+
+#use -01 on armhf to avoid assembler errors
+ifeq ($(DEB_HOST_ARCH),armhf)
+ export CFLAGS += -O1
+endif
+
autoreconf: autoreconf-stamp
autoreconf-stamp: $(QUILT_STAMPFN)
autoreconf -f -i -s
--- End Message ---
--- Begin Message ---
This has now been fixed on the gcc side.
--- End Message ---
