--- Comment #3 from mikpe at it dot uu dot se 2010-02-03 14:51 ---
gcc-4.4.3 with binutils-2.20 fails StackTrace2 and Throw_3, reverting to
binutils-2.19.1 eliminated those two failures.
Bootstrapping with binutils-2.19.1 but running the test suite with
binutils-2.20 did not trigger
FYI: The status of the gnat-4.4 source package
in Debian's testing distribution has changed.
Previous version: 4.4.2-4
Current version: 4.4.3-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will
gcc-4.5_4.5-20100202-1_multi.changes uploaded successfully to localhost
along with the files:
fixincludes_4.5-20100202-1_i386.deb
gobjc-4.5-multilib_4.5-20100202-1_amd64.deb
libstdc++6_4.5-20100202-1_amd64.deb
gobjc-4.5_4.5-20100202-1_amd64.deb
lib64gomp1-dbg_4.5-20100202-1_i386.deb
Accepted:
cpp-4.5-doc_4.5-20100202-1_all.deb
to main/g/gcc-4.5/cpp-4.5-doc_4.5-20100202-1_all.deb
cpp-4.5_4.5-20100202-1_amd64.deb
to main/g/gcc-4.5/cpp-4.5_4.5-20100202-1_amd64.deb
cpp-4.5_4.5-20100202-1_i386.deb
to main/g/gcc-4.5/cpp-4.5_4.5-20100202-1_i386.deb
There are disparities between your recently accepted upload and the
override file for the following file(s):
lib32gcc1_4.5-20100202-1_amd64.deb: package says priority is optional, override
says extra.
Please note that a list of new sections were recently added to the
archive: cli-mono,
LAST_UPDATED: Obtained from SVN: tags/gcc_4_4_3_release revision 156151
Native configuration is alpha-unknown-linux-gnu
=== libgomp tests ===
Running target unix
=== libgomp Summary ===
# of expected passes2440
=== libstdc++ tests
LAST_UPDATED: Obtained from SVN: tags/gcc_4_4_3_release revision 156151
Target: x86_64-linux-gnu
gcc version 4.4.3 (Debian 4.4.3-2)
Native configuration is x86_64-pc-linux-gnu
=== g++ tests ===
Running target unix
=== g++ Summary for unix ===
# of expected
LAST_UPDATED: Obtained from SVN: tags/gcc_4_4_3_release revision 156151
Target: x86_64-kfreebsd-gnu
gcc version 4.4.3 (Debian 4.4.3-2)
Native configuration is x86_64-pc-kfreebsd-gnu
=== g++ tests ===
Running target unix
=== g++ Summary for unix ===
# of
LAST_UPDATED: Obtained from SVN: tags/gcc_4_4_3_release revision 156151
Target: mipsel-linux-gnu
gcc version 4.4.3 (Debian 4.4.3-2)
Native configuration is mipsel-unknown-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/ipa/iinline-1.C scan-ipa-dump inline
LAST_UPDATED: Tue Feb 2 18:22:40 UTC 2010 (revision 156452)
Target: x86_64-linux-gnu
gcc version 4.5.0 20100202 (experimental) [trunk revision 156452] (Debian
4.5-20100202-1)
Native configuration is x86_64-pc-linux-gnu
=== g++ tests ===
Running target unix
FAIL:
LAST_UPDATED: Tue Feb 2 18:22:40 UTC 2010 (revision 156452)
Target: i486-linux-gnu
gcc version 4.5.0 20100202 (experimental) [trunk revision 156452] (Debian
4.5-20100202-1)
Native configuration is i486-pc-linux-gnu
=== g++ tests ===
Running target unix
===
Package: cpp
Version: 4:4.4.2-3
Severity: normal
Hi,
please, call update-alternatives only in the case the prerm script was
not called with upgrade. If you remove the alternative in the case of an
upgrade, you might destroy the manual selection for the alternative. Use
something like the
--- Comment #14 from bkoz at gcc dot gnu dot org 2010-02-03 23:07 ---
Got it Matthias, fixing, thanks for explaining what's up.
How do you get these errors and validate the generated man pages? If it's a
script can you attach it? Are you re-configuring doxygen? Or is this
--- Comment #15 from bkoz at gcc dot gnu dot org 2010-02-04 00:16 ---
markup options
/**
* @brief Flags access.
* @return The minimum field width to generate on output operations.
*
* Minimum field width refers to the number of characters.
*
*
14 matches
Mail list logo
