[Bug 836588] Re: armel FTBFS with gcc 4.5 org 4.6 O2 and fPIC

Launchpad Bug Tracker 836588 at bugs.launchpad.net
Wed Jan 11 14:45:12 UTC 2012


This bug was fixed in the package gmime2.4 - 2.4.31-0ubuntu2

---------------
gmime2.4 (2.4.31-0ubuntu2) precise; urgency=low

  * debian/rules: No longer force -O1 on armel, it causes a FTBFS
    similar to the one it worked-around last cycle. The -O2 default
    works now. This syncs up armel and armhf again, the latter did not
    have the work-around in Oneiric (LP: #836588)
 -- Jani Monoses <jani at ubuntu.com>   Wed, 11 Jan 2012 16:36:25 +0200

** Changed in: gmime2.4 (Ubuntu)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gcc-4.5 in Ubuntu.
https://bugs.launchpad.net/bugs/836588

Title:
  armel FTBFS with gcc 4.5 org 4.6 O2 and fPIC

Status in The GNU Compiler Collection:
  In Progress
Status in Linaro GCC:
  Triaged
Status in “gcc-4.5” package in Ubuntu:
  Confirmed
Status in “gcc-4.6” package in Ubuntu:
  Confirmed
Status in “gmime2.4” package in Ubuntu:
  Fix Released

Bug description:
  A reference to an inexistent label in the asm file causes FTBFS.
  Using -O1 or dropping -fPIC works fine, so does gcc-4.4 with O2 and fPIC on.

  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../util -DGMIME_VERSION=\"2.4.26\" -DGMIME_MAJOR_VERSION=2 -DGMIME_MINOR_VERSION=4 -DGMIME_MICRO_VERSION=26 -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-gnueabi/glib-2.0/include  -O2  -c gmime-param.c  -fPIC  -o .libs/gmime-param.o
  /tmp/ccDqUYcb.s: Assembler messages:
  /tmp/ccDqUYcb.s:1153: Error: can't resolve `.rodata' {.rodata section} - `.LPIC20' {*UND* section}

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/836588/+subscriptions




More information about the foundations-bugs mailing list