Bug#554574: libstdc++6: apt segfaults on hppa
On Mon, Nov 23, 2009 at 8:48 AM, Aurelien Jarno wrote: >> Next steps: >> (1) Wait for testsuite results to finish completely. Verify nothing >> has regressed. No regressions. >> (2) Remove changes to gcc package debian/rules2 and re-run validation. Some regressions caused by enabling cloog/ppl, however these regressions do not break the libstdc++6 package in any critical way. Re-running the test case by hand now works, and the C++ class has the correct offsets. >> (3) In parallel provide new patch to debian-glibc to fix alignment >> issues with pthread types. Done. >> (4) Ask debian-glibc team to run a build and look for testsuite regressions. Done. >> If the test results for (2) and (4) are clean, then I will give the >> green light for a new glibc to be uploaded. This will fix the >> libstdc++6 issues. The test results for (2) and (4) are clean enough for a release given my QA. > I guess there is a fifth step need: > (5) rebuild gcc-4.4 against the fixed glibc. Aurelian has uploaded a new glibc with the fix and informs me that gcc is currently rebuilding. Once I conform that the newly built gcc is OK, we can close this issue and start building packages again. Cheers, Carlos. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
gcc-4.3 4.3.4-6 MIGRATED to testing
FYI: The status of the gcc-4.3 source package in Debian's testing distribution has changed. Previous version: 4.3.4-5 Current version: 4.3.4-6 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See http://release.debian.org/testing-watch/ for more information. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Results for 4.3.4 (Debian 4.3.4-6) testsuite on mipsel-unknown-linux-gnu
LAST_UPDATED: Mon Nov 2 00:19:31 UTC 2009 (revision 153796) Target: mipsel-linux-gnu gcc version 4.3.4 (Debian 4.3.4-6) Native configuration is mipsel-unknown-linux-gnu === g++ tests === Running target unix === g++ Summary for unix === # of expected passes17671 # of expected failures 92 # of unsupported tests 140 Running target unix/-mabi=64 FAIL: g++.dg/other/anon5.C (test for excess errors) === g++ Summary for unix/-mabi=64 === # of expected passes17642 # of unexpected failures1 # of expected failures 92 # of unsupported tests 142 Running target unix/-mabi=n32 === g++ Summary for unix/-mabi=n32 === # of expected passes17675 # of expected failures 92 # of unsupported tests 140 === g++ Summary === # of expected passes52988 # of unexpected failures1 # of expected failures 276 # of unsupported tests 422 /build/buildd-gcc-4.3_4.3.4-6-mipsel-WqupoI/gcc-4.3-4.3.4/build/gcc/testsuite/g++/../../g++ version 4.3.4 (Debian 4.3.4-6) === gcc tests === Running target unix === gcc Summary for unix === # of expected passes48257 # of expected failures 91 # of untested testcases 35 # of unsupported tests 344 Running target unix/-mabi=64 FAIL: gcc.misc-tests/linkage.c link === gcc Summary for unix/-mabi=64 === # of expected passes47916 # of unexpected failures1 # of expected failures 91 # of untested testcases 35 # of unsupported tests 405 Running target unix/-mabi=n32 FAIL: gcc.c-torture/compile/20080806-1.c -O1 (internal compiler error) FAIL: gcc.c-torture/compile/20080806-1.c -O1 (test for excess errors) FAIL: gcc.misc-tests/linkage.c link === gcc Summary for unix/-mabi=n32 === # of expected passes47888 # of unexpected failures3 # of expected failures 91 # of untested testcases 35 # of unsupported tests 410 === gcc Summary === # of expected passes144061 # of unexpected failures4 # of expected failures 273 # of untested testcases 105 # of unsupported tests 1159 /build/buildd-gcc-4.3_4.3.4-6-mipsel-WqupoI/gcc-4.3-4.3.4/build/gcc/xgcc version 4.3.4 (Debian 4.3.4-6) === gfortran tests === Running target unix === gfortran Summary for unix === # of expected passes24738 # of expected failures 3 # of unsupported tests 140 Running target unix/-mabi=64 === gfortran Summary for unix/-mabi=64 === # of expected passes24986 # of expected failures 3 # of unsupported tests 20 Running target unix/-mabi=n32 === gfortran Summary for unix/-mabi=n32 === # of expected passes24986 # of expected failures 3 # of unsupported tests 20 === gfortran Summary === # of expected passes74710 # of expected failures 9 # of unsupported tests 180 /build/buildd-gcc-4.3_4.3.4-6-mipsel-WqupoI/gcc-4.3-4.3.4/build/gcc/testsuite/gfortran/../../gfortran version 4.3.4 (Debian 4.3.4-6) === obj-c++ tests === Running target unix UNRESOLVED: obj-c++.dg/lookup-2.mm compilation failed to produce executable UNRESOLVED: obj-c++.dg/try-catch-2.mm compilation failed to produce executable UNRESOLVED: obj-c++.dg/try-catch-9.mm compilation failed to produce executable === obj-c++ Summary === # of expected passes437 # of expected failures 9 # of unresolved testcases 3 # of unsupported tests 13 /build/buildd-gcc-4.3_4.3.4-6-mipsel-WqupoI/gcc-4.3-4.3.4/build/gcc/testsuite/obj-c++/../../g++ version 4.3.4 (Debian 4.3.4-6) === objc tests === Running target unix === objc Summary === # of expected passes1832 # of expected failures 7 # of unsupported tests 24 /build/buildd-gcc-4.3_4.3.4-6-mipsel-WqupoI/gcc-4.3-4.3.4/build/gcc/xgcc version 4.3.4 (Debian 4.3.4-6) === libgomp tests === Running target unix WARNING: program timed out. FAIL: libgomp.c/appendix-a/a.18.1.c execution test WARNING: program timed out. FAIL: libgomp.fortran/appendix-a/a.18.1.f90 -O3 -fomit-frame-pointer -funroll-loops execution test FAIL: libgomp.fortran/reference1.f90 -O1 execution test FAIL: libgomp.fortran/reference1.f90 -O2 execution test FAIL: libgomp.fortran/reference1.f90 -O3 -fomit-frame-pointer execution test FAIL: libgomp.fortran/reference1.f90 -O3 -fomit-frame-pointer -funroll-loops execution test FAIL: libgomp.fortran/reference1.f90 -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions execution test FAIL:
Re: Switch on compiler hardening defaults
["Followup-To:" header set to gmane.linux.debian.devel.general.] On 2009-11-05, Kees Cook wrote: >> The majority of distributions does turn on these options during >> package build time, which IMO is the right thing to do. Debian >> should do the same. There's now Raphael's new framework in place >> which makes the injection of macros in dpkg-buildpackage in the >> environment obsolete. > > This would certainly be better than nothing, and better than the > hardening-wrapper package, but it would require that every package in > Debian be modified to respect external environments. Also, I think > having the compiler itself be hardened is the bigger win. If doko feels uncomfortable with appyling the patches, we should use the dpkg-buildpackage way (which I'm technically fine with). It also has the nice side effect that we get a central place where we can opt out architecture which don't implement a specific hardening feature. It also allows maintainers to specifically opt out in cases where they feel the overhead to be inacceptably high. (e.g., a number-crunching math application). > Out of curiosity, where can I and others find the documentation for the > dpkg-buildpackage environment framework? We should immediately add the > hardening options to it now for the packages that it will work on. See dpkg-buildpackage(1) in the section "ENVIRONMENT VARIABLES" What flags do you intend to enable? -Wformat, -Wformat-security, -D_FORTIFY_SOURCE=2 and -fstack-protector ? Could you file a bug against dpkg-dev? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#554574: libstdc++: small test program
Package: libstdc++6
Severity: normal
It sounds like this bug is the cause of a FTBFS in one of my packages. In
case it's helpful, here is a small self-contained test program that currently
crashes when run on the hppa buildd:
#include
#include
int
main(void)
{
std::ofstream ofs("_conftest.dat");
for (int i = 0; i < 5; i++)
ofs << "0123456789\r\n";
ofs.close();
return EXIT_SUCCESS;
}
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.31-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages libstdc++6 depends on:
ii gcc-4.4-base 4.4.2-3The GNU Compiler Collection (base
ii libc6 2.10.2-1 GNU C Library: Shared libraries
ii libgcc1 1:4.4.2-3 GCC support library
libstdc++6 recommends no packages.
libstdc++6 suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
[Bug c++/5458] address of overloaded template function as argument for template
--- Comment #14 from jason at gcc dot gnu dot org 2009-11-25 02:55 --- I'm not sure the standard actually says that this is well-formed, though it seems reasonable to me. 13.4/2: If the name is a function template, template argument deduction is done (14.9.2.2), and if the argument deduction succeeds, the resulting template argument list is used to generate a single function template specialization, which is added to the set of overloaded functions considered. 14.9.2.2: The function templates function type and the specified type are used as the types of P and A, and the deduction is done as described in 14.9.2.5. It's not entirely clear that there is a "specified type" for this kind of two-way deduction. EDG also rejects this. -- jason at gcc dot gnu dot org changed: What|Removed |Added CC||jason at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=5458 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#557905: Needs bootstrapping on at least mips
Package: gnat-4.4 Version: 4.4.2-3 Severity: serious Hi gnat-4.4 needs gnat-4.4 (>= 4.4.2-1) for building which is not availalble on mips. This blocks the testing migration of gcc-defaults and as such many other packages. Cheers Luk -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#557905: Needs bootstrapping on at least mips
Luk Claes a écrit : > Package: gnat-4.4 > Version: 4.4.2-3 > Severity: serious > > Hi > > gnat-4.4 needs gnat-4.4 (>= 4.4.2-1) for building which is not availalble on > mips. This blocks the testing migration of gcc-defaults and as such many > other packages. I am currently bootstraping it, but on a very slow machine. The build has been started a few days ago, and will probably finish by tomorrow (currently running the testsuite). -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
