fix building glibc-2.16 using GCC-4.7

Bug #1062343 reported by Matthias Klose
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gcc-4.7 (Debian)
Fix Released
Unknown
gcc-4.7 (Ubuntu)
Fix Released
Medium
Unassigned
Quantal
Won't Fix
Medium
Unassigned

Bug Description

4.7.2-2ubuntu1 has a local patch to address PR c/33763, which is wrong, and causes glibc fail to build. Replaced in 4.7.2-3ubuntu1 by the fix taken from the 4.7 branch.

Related branches

Matthias Klose (doko)
Changed in gcc-4.7 (Ubuntu Quantal):
importance: Undecided → Medium
milestone: none → quantal-updates
status: New → Confirmed
Changed in gcc-4.7 (Debian):
status: Unknown → New
Changed in gcc-4.7 (Debian):
status: New → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gcc-4.7 - 4.7.2-5ubuntu1

---------------
gcc-4.7 (4.7.2-5ubuntu1) quantal; urgency=low

  * Merge with Debian.

gcc-4.7 (4.7.2-5) UNRELEASED; urgency=low

  * Update to SVN 20121015 (r192393) from the gcc-4_7-branch.

  [ Matthias Klose ]
  * Update the Linaro support to the 4.7-2012.10 release.
  * Define MULTIARCH_DIRNAME for arm64 (Wookey).
  * Let the lib*objc-dev packages depend on the lib*gcc-dev packages.
  * Let the libstdc++-dev package depend on the libgcc-dev package.
  * Drop the dependency of the libstdc++-dev package on g++, make
    libstdc++-dev Multi-Arch: same. Closes: #678623.
  * Install override files before calling dh_fixperms.
  * Backport the libffi arm64 port.

  [ Thibaut Girka ]
  * Split out lib*gcc-dev packages.
  * Split out lib*objc-dev packages.
 -- Matthias Klose <email address hidden> Tue, 16 Oct 2012 00:42:44 +0200

Changed in gcc-4.7 (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Rolf Leggewie (r0lf) wrote :

quantal has seen the end of its life and is no longer receiving any updates. Marking the quantal task for this ticket as "Won't Fix".

Changed in gcc-4.7 (Ubuntu Quantal):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.