closing the jaunty task as won't fix
** Changed in: gcc-4.3 (Ubuntu Jaunty)
Status: In Progress => Won't Fix
--
gcc-4.3 does not pass its own testsuite with Ubuntu compiler flags
https://bugs.launchpad.net/bugs/344502
You received this bug notification because you are a member of Ubuntu
B
fixed in gcc-4.3 (4.3.3-8ubuntu1) karmic
** Changed in: gcc-4.3 (Ubuntu)
Status: In Progress => Fix Released
--
gcc-4.3 does not pass its own testsuite with Ubuntu compiler flags
https://bugs.launchpad.net/bugs/344502
You received this bug notification because you are a member of Ubuntu
** Also affects: gcc-4.3 (Ubuntu Jaunty)
Importance: Medium
Assignee: Matthias Klose (doko)
Status: In Progress
** Changed in: gcc-4.3 (Ubuntu Jaunty)
Milestone: later => jaunty-updates
--
gcc-4.3 does not pass its own testsuite with Ubuntu compiler flags
https://bugs.launchpa
Can this be applied to gcc-snapshot and gcc-4.4? I assume it's not
wanted for gcc-4.3?
** Changed in: gcc-4.3 (Ubuntu)
Assignee: Kees Cook (kees) => Matthias Klose (doko)
--
gcc-4.3 does not pass its own testsuite with Ubuntu compiler flags
https://bugs.launchpad.net/bugs/344502
You receiv
As mentioned on IRC, this is due to the pch.exp-specific work-around for
bug 346126. The pch.exp patch can be dropped once the patch for 346126
has been applied. (And has been dropped already from the above split-
out patches.)
--
gcc-4.3 does not pass its own testsuite with Ubuntu compiler fla
running the testsuite for a build on Debian unstable, without the
hardening default patches applied, I see the following regressions when
the patch in comment 2 is applied:
--- test-summary-unpatched 2009-03-23 16:55:42.0 +
+++ test-summary2009-03-24 01:02:44.0 +00
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39536
(testsuite-hardening-fortify.patch)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39537
(testsuite-hardening-format.patch)
The other two patches are fairly Ubuntu-specific.
--
gcc-4.3 does not pass its own testsuite with Ubuntu compiler flags
htt
Patches split out:
mudflap-hardening-drop.patch: make mudflap (and tests) not compile with
stack-protector or fortify.
testsuite-hardening-format.patch: force -Wno-format for tests that need it.
testsuite-hardening-fortify.patch: check more functions to avoid complaints
from -D_FORTIFY_SOURCE=2.
** Attachment added: "testsuite-hardening-printf-types.patch"
http://launchpadlibrarian.net/24299273/testsuite-hardening-printf-types.patch
--
gcc-4.3 does not pass its own testsuite with Ubuntu compiler flags
https://bugs.launchpad.net/bugs/344502
You received this bug notification because y
** Attachment added: "testsuite-hardening-fortify.patch"
http://launchpadlibrarian.net/24299237/testsuite-hardening-fortify.patch
--
gcc-4.3 does not pass its own testsuite with Ubuntu compiler flags
https://bugs.launchpad.net/bugs/344502
You received this bug notification because you are a m
** Attachment added: "testsuite-hardening-format.patch"
http://launchpadlibrarian.net/24299231/testsuite-hardening-format.patch
--
gcc-4.3 does not pass its own testsuite with Ubuntu compiler flags
https://bugs.launchpad.net/bugs/344502
You received this bug notification because you are a mem
Debdiff against gcc-snapshot, but needs some work to break out the
libmudflap changes.
** Attachment added: "gcc-snapshot_20090225-0ubuntu2.debdiff"
http://launchpadlibrarian.net/24202214/gcc-snapshot_20090225-0ubuntu2.debdiff
--
gcc-4.3 does not pass its own testsuite with Ubuntu compiler fl
** Attachment added: "testsuite-cleanup.dpatch"
http://launchpadlibrarian.net/24028028/testsuite-cleanup.dpatch
** Attachment removed: "testsuite-cleanup.patch"
http://launchpadlibrarian.net/24020082/testsuite-cleanup.patch
** Description changed:
Binary package hint: gcc-4.3
The
** Attachment added: "testsuite-cleanup.patch"
http://launchpadlibrarian.net/24020082/testsuite-cleanup.patch
--
gcc-4.3 does not pass its own testsuite with Ubuntu compiler flags
https://bugs.launchpad.net/bugs/344502
You received this bug notification because you are a member of Ubuntu
Bugs
14 matches
Mail list logo
