Bug#657682: gcc-4.6: assembler error on armhf Error: can't resolve `.rodata' {.rodata section} - `.LPIC10' {*UND* section}
Package: gcc-4.6
Version: 4.6.2-12
Severity: important
Gmime failed to build on armhf with the following error
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 reduced this to the attatched testcase, to build the testcase use the
following command.
gcc -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -O2 -c test.c -fPIC
I attempted to reduce it further but any further significant code removals
I did made the error go away.
removing -fPIC makes the error go away as does reducing the optimisation level
to -O1
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: armhf (armv7l)
Kernel: Linux 2.6.39.2-x2 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gcc-4.6 depends on:
ii binutils 2.22-4
ii cpp-4.6 4.6.2-12
ii gcc-4.6-base 4.6.2-12
ii libc6 2.13-24
ii libgcc1 1:4.6.2-12
ii libgmp10 2:5.0.2+dfsg-2+b1
ii libgomp1 4.6.2-12
ii libmpc2 0.9-4+b1
ii libmpfr4 3.1.0-3+b1
ii zlib1g 1:1.2.3.4.dfsg-3+b1
Versions of packages gcc-4.6 recommends:
ii libc6-dev 2.13-24
Versions of packages gcc-4.6 suggests:
pn binutils-gold <none>
pn gcc-4.6-doc <none>
pn gcc-4.6-locales <none>
pn libgcc1-dbg <none>
pn libgomp1-dbg <none>
pn libmudflap0-4.6-dev <none>
pn libmudflap0-dbg <none>
pn libquadmath-dbg <none>
-- no debconf information
Reply to: