touch-packages team mailing list archive

[Timo Jyrinki <timo.jyrinki@xxxxxxxxxxxxx>]

Just to collect information in this bug, the fPIC requirement and fPIE
banning in Qt now is because of this:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65886

This bug originally however is about a problem that shows up when that
related Bsymbolic option is enabled on armhf too. This needed forcing
but we forced it at one point since it was believed the toolchain bug
was fixed. However, for now it remains disabled on non-x86 (the default
of Qt upstream) because of the persisting bug, but it may be re-enabled
later if the bug is resolved.

The toolchain bug (fPIC + Bsymbolic misbehaving on arm) is last
described at https://bugreports.qt.io/browse/QTBUG-47350

** Bug watch added: GCC Bugzilla #65886
   https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65886

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1403758

Title:
  Unity8 shows black screen with Qt 5.4.0

Status in binutils:
  Unknown
Status in binutils package in Ubuntu:
  Incomplete
Status in gcc-defaults package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  With bug #1403511 taken care of in Qt, apps do not anymore crash with
  Qt 5.4 and device does not anymore go into reboot loop. However,
  nothing is visible on the screen.

  It seems unity8, unity8-dash etc are all running. unity8.log attached

  Relevant upstream links referring GCC5 as the reason to require -fPIC:
  http://code.qt.io/cgit/qt/qtbase.git/commit/?id=36d6eb721e7d5997ade75e289d4088dc48678d0d
  http://code.qt.io/cgit/qt/qtbase.git/commit/?id=3eca75de67b3fd2c890715b30c7899cebc096fe9

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